Method and system for computer based testing using an amalgamated resource file

ABSTRACT

A system for computer-based testing for producing a test and delivering the test to an examinee includes a storage device that has a first storage location, which stores a first segment of a test definition language, and a second storage location, which stores a second segment of the test definition language, a validation expansion module that validates the first segment and the second segment of the test definition language, a test packager that amalgamates the first storage location and the second storage location and transmits the amalgamated segment to the validation expansion module such that the validation expansion module can determine whether the amalgamated segment forms a complete and valid set, and a test driver that has an executable code that controls functionality that enables the test driver to deliver the test to an examinee.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is related to and claims the priority of U.S. Provisional Application Ser. No. 60/331,229, filed Nov. 13, 2001 and incorporated herein by reference, and is further related to:. U.S. Patent Application entitled “EXTENSIBLE EXAM LANGUAGE (XXL) PROTOCOL FOR COMPUTER BASED TESTING” and having inventors Clarke Daniel Bowers, Tronster Maxwell Hartley, Kyle Michael Kvech, and William Howard Garrison (Docket No. 26119-146); U.S. Patent Application entitled “METHOD AND SYSTEM FOR COMPUTER BASED TESTING USING CUSTOMIZABLE TEMPLATES” and having inventor Clarke Daniel Bowers (Docket No. 26119-143); U.S. Patent Application entitled “METHOD AND SYSTEM FOR COMPUTER BASED TESTING USING A NON-DETERMINISTIC EXAM EXTENSIBLE LANGUAGE (XXL) PROTOCOL” and having inventor Clarke Daniel Bowers (Docket No. 26119-144); and U.S. Patent Application entitled “METHOD AND SYSTEM FOR COMPUTER BASED TESTING USING PLUGINS TO EXPAND FUNCTIONALITY OF A TEST DRIVER” and having inventor Clarke Daniel Bowers (Docket No. 26119-142) all of which are being filed concurrently herewith and all of which are incorporated by reference in their entirety herein.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention generally relates to the field of computer-based testing, and in particular, the present invention relates to amalgamating an exam resource file to combine first defined and later defined test content and specification of a computer-based test to reduce the amount of authored XXL and to reduce the size of the size of the exam resource file during delivery of the computer-based test to an examinee.

2. Background of the Related Art

For many years, standardized testing has been a common method of assessing examinees as regards educational placement, skill evaluation, etc. Due to the prevalence and mass distribution of standardized tests, computer based testing has emerged as a superior method for providing standardized tests, guaranteeing accurate scoring, and ensuring prompt return of test results to examinees.

Tests are developed based on the requirements and particulars of test developers. Typically, test developers employ psychometricians or statisticians and psychologists to determine the specific requirements specific to human assessment. These experts often have their own, unique ideas regarding how a test should be presented and regarding the necessary contents of that test, including the visual format of the test as well as the data content of the test. Therefore, a particular computer based test has to be customized to fulfill the client's requirements.

FIG. 1 illustrates a prior art process for computerized test customization, denoted generally by reference numeral 10. First, a client details the desired test requirements and specifications, step 12. The computerized test publisher then creates the tools that allow the test publisher to author the items, presentations, etc., required to fulfill the requirements, step 14. The test publisher then writes an item viewer, which allows the test publisher to preview what is being authored, step 16.

An item presenter is then written to present the new item, for example, to the test driver, step 18. Presenting the new item to the test driver requires a modification of the test driver's executable code. The test driver must be modified so that it is aware of the new item and can communicate with the new item presenter, step 20. The test packager must then also be modified, step 22. The test packager, which may also be a compiler, takes what the test publisher has created and writes the result as new object codes for the new syntax. Subsequently, the scoring engine must also be modified to be able to score the new item type, step 24. Finally, the results processor must be modified to be able to accept the new results from the new item, step 26. This process requires no less than seven software creations or modifications to existing software.

During authoring of the test, the test author might desire to define some portion of the test specification for re-use. Alternatively the test author might redefine or override certain portions of the test specification that were defined early in the test specification. Previous test definition languages attempted to solve this problem by repeating selected pieces of the test specification at a higher level of the delivery hierarchy. However, it has been determined that this solution does not cover the content of the test specification and assumes that the pattern of repetition is based on the unit of delivery. For example, test specification based on the order of delivery and the hierarchy may be: a two-section exam of math followed by English. All math questions have a minimum response value of 2 and all English questions minimum response value of 3. An example that will not support repetition of test definition is a two-section exam of math and English. Where half the math questions have a minimum response of 2 and the other half of the math questions have a minimum response of 3. In this situation, the hierarchy does not match the pattern of repetition.

Furthermore, it has been determined that this solution requires specific units of the test to have detailed knowledge of shared specification and to communicate the shared specification to other units of the test.

U.S. Pat. No. 5,827,070 (Kershaw et al.) and U.S. Pat. No. 5,565,316 (Kershaw et al.) are incorporated herein by reference. The '070 and '316 patents, which have similar specifications, disclose a computer-based testing system comprising a test development system and a test delivery system. The test development system comprises a test document creation system for specifying the test contents, an item preparation system for computerizing each of the items in the test, a test preparation system for preparing a computerized test, and a test packaging system for combining all of the items and test components into a computerized test package. The computerized test package is then delivered to authorized examinees on a workstation by the test delivery system.

FIG. 2 illustrates the relationship among session scripts 30, test scripts 32, and units. A script consists of a series of files and further specifies the option settings and configuration data, which the Test Delivery Application (TDA) needs for operation. During test preparation, scripts are prepared and combined with the items prepared during item preparation. Scripts control the sequence of events during a testing session. Two types of scripts are preferably used, for example: the session script 30 and one or more test scripts 32. The session script 30 controls the order in which units within the testing session are presented. Units provide specific services to the examinee, such as delivering a test or presenting a score report. Just as the session script controls the session, the test script controls what is presented to the examinee during the testing unit. Each testing unit may include one or more delivery units, which are separately timed and scored subdivisions of a test. The system can dynamically select, or spiral, scripts and other test components so that examinees are given what appear to be different tests. FIG. 24 shows the relationship among session scripts 30, test scripts 32, and units.

The session script is the second-level component of the testing package. It performs two primary functions: First, it specifies the Session Control Information, which defines the default options that are in effect for the entire examinee testing session. Second, it controls the order in which units within the testing session are presented and the options used to present them. The units that can be presented within a session script are: General information screen units, Tutorial units, Break units, Data collection units, Scoring and Reporting units, and Testing units.

The session control information contains the default options in effect for the entire session. Control information can be provided at multiple levels within the testing session. Thus, the control information provided at the session level can be overridden by information that occurs later in the session. The information provided at the session level would generally include the following: Name—the session script name to be used by administrators in selecting a specific session script from Administrative Application menus; Input device—the input device to be used during the session (e.g., mouse or keyboard); Color—the colors to be used during the session; Messages—program-specific messages to override default messages during the session; Demo Script—indicates whether the script presents a demonstration or operational test; Research Indicator—indicates whether the script presents a research pilot test; Special Timing—indicates whether the script is standard or specially timed version.

The testing unit presents a test, based on the contents of a test script that may have been selected at runtime. The following units can be included within a testing unit: general information screen unit; tutorial unit; break unit; delivery unit, which delivers items to the examinee. This permits testing programs to interleave general information screens, tutorials, and breaks with sections of a test. The testing unit contains the following information: script selection mode indicates whether dynamic runtime selection is to be used to select the test script; reference to a test script which controls the sequence of events and options used during the testing unit. If dynamic runtime selection is to be used, the reference is to a set of test scripts. Like the session script, the test script performs two primary functions. First, it specifies the test and delivery unit control information. Test control information defines the options that are in effect for the testing unit. Delivery unit control information defines the options that are in effect for a particular delivery unit within a testing unit. It controls the order in which units are presented within the testing unit and the options used to present them. The rules for presentation of units are the same as those for the session script, except that an additional unit, the delivery unit, can be included within a test script.

U.S. Pat. No. 5,513,994 (Kershaw et al.), which is incorporated herein by reference, discloses a centralized administrative system and method of administering standardized test to a plurality of examinees. The administrative system is implemented on a central administration workstation and at least one test workstation located in different rooms at a test center. The administrative system software, which provides substantially administrative functions, is executed from the central administration workstation. The administrative system software, which provides function carried out in connection with a test session, is executed from the testing workstations.

None of the Kershaw et al. patents appear to make any mention of a test definition language that does not required the overriding language to be repeated at higher levels of the delivery hierarchy. What is required is a computer based testing system that supports a non-deterministic test definition language that, for example, allows subsequent specifications to be added to the test definition language without requiring repetitive definitions and that enables a reduction in size of exam source files, and an exam resource file, which contains the test definition language during delivery of the test. Other features and advantages in addition to the above, or in the alternative to the above, are described in the Summary of the Invention and the Detailed Descriptions provided below.

SUMMARY OF THE INVENTION

It is one feature and advantage of the present invention to amalgamate test specification and content to reduce the size of a resource file that contains the test specification and content, where a test driver and an expansion module uses the test specification and content to deliver a test to an examinee.

It is another optional feature and advantage of the present invention to allow a test publisher to define different aspects of test specification and content for a particular feature of the test in multiple locations and to amalgamate those multiple locations at the time of delivery of the test such that the test publisher does not have to repeat the same aspects if the test specification and content for the particular feature at the multiple locations.

It is another optional feature and advantage of the present invention to allow later defined elements of a particular feature to override previously defined elements that exist at a higher level of the test specification and contents.

It is another optional feature and advantage of the present invention to allow later defined elements to define previously omitted non-common test specification and contents.

It is another optional feature and advantage of the present invention that specific units of the test need not have detailed knowledge of shared specification and need not communicate the shared specification with other units of the test.

These and other features and advantages of the present invention are achieved in a system for computer-based testing for producing a test and delivering the test to an examinee. The test has a presentation format that determines the visual presentation of the test and data content that determines the functional properties of the test. The system includes a storage device that has a first storage location and a second storage location. The first storage location stores a first segment of a test definition language and the second storage location stores a second segment of the test definition language. The first segment and the second segment define information comprising at least one of the data content, the presentation format, progression, scoring, printing, timing, and/or results reporting of the test. In an alternative embodiment, the first segment and the second segment of the test definition language further comprise the same category of information, where the category is at least one of the data content, the presentation format, the progression, the scoring, the printing, the timing, and/or the results reporting of the test.

The system also includes a validation expansion module that validates the first segment and the second segment of the test definition language by determining whether the first segment and the second segment are correctly formatted. The validation expansion module also stores the first segment to one of the first storage location and the second storage location and the second segment to another one of the first storage location and the second storage location in the storage device. In an alternative embodiment, the validation expansion module is a plugin.

The system further includes a test packager that transmits the first segment and the second segment of the test definition language to the validation expansion module during delivery of the test. The test packager determines to which of the first storage location and the second storage location in the storage device the first segment and the second segment are stored by the validation expansion module. The test packager also amalgamates the first storage location and the second storage location and stores an amalgamated segment of the test definition language in a first virtual storage location and transmits the amalgamated segment to the validation expansion module such that the validation expansion module can determine whether the amalgamated segment forms a complete and valid set of the first segment and second segment of the test definition language. In an alternative embodiment, the test packager is a compiler.

The system further includes a test driver that has an executable code that controls functionality that enables the test driver to deliver the test to an examinee using a display device, manage the test, control the progression of the test, control the scoring of the test, control the printing of the test, control the timing of the test, and control the results reporting of the test based on the test definition language. During delivery of the test, the test driver amalgamates the first storage location and the second storage location into a second virtual storage location such that the validation expansion module can retrieve the amalgamated segment from the second virtual storage location to enable the functionality of the test driver.

In another embodiment of the present invention, a system for computer-based testing includes a storage device that has a first storage location, a second storage location, and a third storage location. The first storage location stores a first segment of a test definition language, the second storage location stores a second segment of the test definition language, and the third storage location stores a third segment of the test definition language. The first segment, the second segment, and the third segment comprise at least one of the data content, the presentation format, progression, scoring, printing, timing, and/or results reporting of the test. In an alternative embodiment, the first segment, the second segment, and the third segment of the test definition language further comprise the same category of information, where the category is at least one of the data content, the presentation format, the progression, the scoring, the printing, the timing, and the results reporting of the test.

The system also includes a validation expansion module that validates the first segment, the second segment, and the third segment of the test definition language, and stores the first segment to one of the first storage location, the second storage location, and the third storage location, the second segment to another one of the first storage location, the second storage location, and the third storage location, and the third segment to another one of the first storage location, the second storage location, and the third storage location. In an alternative embodiment, the validation expansion module is a plugin.

The system further includes a test packager that transmits the first segment, the second segment, and the third segment of the test definition language to the validation expansion module during production of the test such that the validation expansion module is capable of validating the first segment, the second segment, and the third segment. The test packager determines to which of the first storage location, the second storage location, and the third storage location in the storage device the first segment, the second segment, and the third segment are stored by the validation expansion module. The test packager also amalgamates the first storage location, the second storage location, and the third storage location and stores an amalgamated segment of the test definition language in a first virtual storage location, and transmits the amalgamated segment to the validation expansion module such that the validation expansion module is capable of determining a complete and valid set of the first segment, the second segment, and the third segment of the test definition language. In an alternative embodiment, the test packager is a compiler.

The system also includes a test driver that has an executable code that controls functionality performed by the test driver that enables the test driver to deliver the test to an examinee using a display device, manage the test, control progression of the test, control scoring of the test, control printing of the test, control timing of the test, and control reporting of test results based on the test definition language. During delivery of the test, the test driver amalgamates the first storage location, the second storage location, and the third storage location into a second virtual storage location such that the validation expansion module is capable of retrieving the amalgamated segment from the second virtual storage location to enable the functionality of the test driver.

In another embodiment of the present invention, a method of computer-based testing for a test is provided, where the test has a presentation format that determines the visual presentation of the test and data content that determines the functional properties of the test. Delivery of the test is controlled by a test driver that has an executable code that enables the test driver to deliver the test to an examinee using a display device, manage the test, control progression of the test, control scoring of the test, control printing of the test, control timing of the test, and control results reporting of the test.

The method includes the sequential, non-sequential, and/or sequence independent steps of validating a first segment of the test definition language during a test production cycle and validating a second segment of the test definition language during the test production cycle. The first segment and the second segment define information comprising at least one of the data content, the presentation format, progression, scoring, printing, timing, and/or results reporting of the test. In an alternative embodiment, the first segment and the second segment further define the same category of information, which is at least one of the data content, the presentation format, the progression, the scoring, the printing, the timing, and the results reporting of the test.

The method also include amalgamating the first segment and the second segment of the test definition language during the test production cycle such that an amalgamated segment is formed, validating the amalgamated segment during the test Production cycle, such that a validated amalgamated segment is created and such that the amalgamated segment is valid if the amalgamated segment forms a complete and valid set. The method further includes amalgamating the first segment and the second segment of the test definition language during a test delivery cycle. The validated amalgamated segment is reformed and retrieved by a validation expansion module to enable the functionality of the test driver.

In another embodiment of the present invention, a method for computer-based testing includes validating a first segment of the test definition language during a test production cycle, validating a second segment of the test definition language during the test production cycle, and validating a third segment of the test definition language. The first segment, the second segment, and the third segment define information comprising at least one of the data content, the presentation format, progression, scoring, printing, timing, and/or results reporting of the test. In an alternative embodiment, the first segment, the second segment, and the third segment of the test definition language further define the same category of information, the same category of information being at least one of the data content, the presentation format, the progression, the scoring, the printing, the timing, and the results reporting of the test.

The method also includes amalgamating the first segment, the second segment, and the third segment of the test definition language during the test production cycle, such that an amalgamated segment is formed and validating the amalgamated segment during the test production cycle, such that a validated amalgamated segment is created and such that the amalgamated segment is valid if the amalgamated segment forms a complete and valid set. The method further includes amalgamating the first segment, the second segment, and the third segment of the test definition language during a test delivery cycle, such that the validated amalgamated segment is reformed and retrieved by a validation expansion module to enable the functionality of the test driver.

In another embodiment of the present invention, a method for computer-based testing is provided, which includes defining the presentation format and the data content in at least two locations comprising a plugin element and actual usage of the plugin element on at least one unit of the test, the at least one unit comprising form, section and group associated with the test and amalgamating the presentation format and the data content defined in the two locations by at least one test driver to deliver the test to an examinee.

In another embodiment of the present invention, a method for computer-based testing includes validating by a plugin at least partial exam source information that is received and amalgamating exam resource data associated with the test. The method also includes validating the exam resource data that has been amalgamated to provide a substantially complete amalgamated exam specification and content and delivering the substantially complete amalgamated exam specification and content validated by the validating step.

In another embodiment of the present invention, a method for computer-based testing is provided for a test that has a first presentation format, a second presentation format, a first data content, and a second data content. The method includes defining the first presentation format and the second presentation format in at least two locations comprising a plugin element and actual usage of the plugin element on at least one unit of the test, the at least one unit comprising form, section and group associated with the test. The method further includes defining the first data content and the second data content in at least two locations comprising the plugin element and the actual usage of the plugin element on at least one unit of the test, the at least one unit comprising form, section and group associated with the test. The method also includes amalgamating at least one of the first and second presentation format and the first and second data content defined in the two locations by at least one test driver to deliver the test to an examinee.

There has thus been outlined, rather broadly, the more important features of the invention and several, but not all, embodiments in order that the detailed description thereof that follows may be better understood, and in order that the present contribution to the art may be better appreciated. There are, of course, additional features of the invention that will be described hereinafter and which will form the subject matter of the claims appended hereto.

In this respect, before explaining at least one embodiment of the invention in detail, it is to be understood that the invention is not limited in its application to the details of construction and to the arrangements of the components set forth in the following description or illustrated in the drawings. The invention is capable of other embodiments and, of being practiced and carried out in various ways. Also, it is to be understood that the phraseology and terminology employed herein are for the purpose of description and should not be regarded as limiting.

As such, those skilled in the art will appreciate that the conception, upon which this disclosure is based, may readily be utilized as a basis for the designing of other structures, methods and systems for carrying out the several purposes of the present invention. It is important, therefore, that the claims be regarded as including such equivalent constructions insofar as they do not depart from the spirit and scope of the present invention.

Further, the purpose of the foregoing abstract is to enable the U.S. Patent and Trademark Office and the public generally, and especially the scientists, engineers and practitioners in the art who are not familiar with patent or legal terms or phraseology, to determine quickly from a cursory inspection the nature and essence of the technical disclosure of the application. The abstract is neither intended to define the invention of the application, which is measured by the claims, nor is it intended to be limiting as to the scope of the invention in any way.

These, together with other objects of the invention, along with the various features of novelty, which characterize the invention, are pointed out with particularity in the claims annexed to and forming a part of this disclosure. For a better understanding of the invention, its operating advantages and the specific objects attained by its uses, reference should be had to the accompanying drawings and descriptive matter in which there is illustrated preferred embodiments of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a flow diagram of a prior art method for computerized test customization;

FIG. 2 is a block diagram of a prior art testing script;

FIG. 3 is a schematic diagram of a computer-based testing system according to the present invention;

FIG. 4 is a block diagram illustrating different types of plugins that are used with the computer-based testing system according to the current invention;

FIG. 5 illustrates various components that comprise an exam source file;

FIGS. 6A and 6B are schematic illustrating the components, classes, and interfaces that comprise a test definition language compiler according to the present invention;

FIG. 7 is a schematic illustrating the components that comprise a test driver and a test administration system according to the present invention;

FIGS. 8A and 8B are schematics illustrating the classes and interfaces that comprise the test driver;

FIG. 9 illustrates the interfaces that comprise a structured storage according to the present invention;

FIGS. 10A and 10B are schematics illustrating the classes and interfaces that comprise the structure storage and associated operations;

FIG. 11 is a block diagram of main storage branches of an exam resource file according to the present invention;

FIG. 12 is a block diagram illustrating an exams branch of the exam resource file;

FIG. 13 is a block diagram illustrating a forms branch of the exam resource file;

FIG. 14 is a block diagram illustrating an items branch of the exam resource file;

FIG. 15 is a block diagram illustrating a categories branch of the exam resource file;

FIG. 16 is a block diagram illustrating a templates branch of the exam resource file;

FIG. 17 is a block diagram illustrating a sections branch of the exam resource file;

FIG. 18 is a block diagram illustrating a groups branch of the exam resource file;

FIGS. 19A, 19B, 19C, and 19D are block diagram illustrating an events sub-branch of the groups branch of the exam resource file;

FIG. 20 is a block diagram illustrating a plugins branch of the exam resource file;

FIG. 21 is a block diagram illustrating a data branch of the exam resource file;

FIG. 22 is a block diagram illustrating a form Groups branch of the exam resource file;

FIG. 23 is a block diagram illustrating an attributes branch of the exam resource file;

FIG. 24 is a block diagram illustrating a scripts branch of the exam resource file;

FIG. 25 is a block diagram illustrating a message box branch of the exam resource file;

FIGS. 26A, 26B, 26C, and 26D are block diagrams of an exam instance file according to the present invention;

FIG. 27 is a flow diagram of a method for computerized test customization according to the present invention;

FIG. 28 is a diagram of a life cycle of a plugin according to the present invention;

FIG. 29 is a flow diagram of a process for compiling plugins according to the present invention;

FIGS. 30A, 30B, 30C, and 30D are flow diagrams of a process for delivering plugins to an examinee during a computer-based test;

FIG. 31 is a flow chart illustrating a process for amalgamation of invisible plugins according to the present invention;

FIG. 32 is a flow chart illustrating a process for amalgamation of visible plugins according to the present invention;

FIG. 33 is a flow chart of a process for amalgamation according to the present invention;

FIG. 34 is a flow chart for a process for validating exam source according to the present invention;

FIG. 35 is a flow chart for a process for validating amalgamated test specification and content using a plugin according to the present invention;

FIG. 36 is a flow chart for a process of delivering amalgamated test specification and content using a test driver and a plugin according to the present invention; and

FIG. 37 is a flow diagram for an example of amalgamation of test specification and content relating to items according to the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Reference now will be made in detail to the presently preferred embodiments of the invention. Such embodiments are provided by way of explanation of the invention, which is not intended to be limited thereto. In fact, those of ordinary skill in the art may appreciate upon reading the present specification and viewing the present drawings that various modifications and variations can be made.

For example, features illustrated or described as part of one embodiment can be used on other embodiments to yield a still further embodiment. Additionally, certain features may be interchanged with similar devices or features not mentioned yet which perform the same or similar functions. It is therefore intended that such modifications and variations are included within the totality of the present invention.

The present invention discloses a system and method of computer-based testing using a test driver that is, for example, object-oriented and is architected to dynamically add functionality through, for example, the use of an expansion module, and preferably through the use of plugins. The test driver preferably references component object model servers using standard interfaces, and uses, for example, class names (that can be an Active Document) defined in a custom test definition language entitled eXtensible eXam Language (“XXL”) based on eXtensible Markup Language (“XML”) format to interact with existing applications while offering the flexibility of allowing development of new plugins. These new plugins can be customized to a client's needs without changing the core test driver. The specific format and protocol of XXL is also described in the co-pending application filed on the same date, entitled “EXTENSIBLE EXAM LANGUAGE (XXL) PROTOCOL FOR COMPUTER BASED TESTING,” incorporated herein by reference.

The plugins advantageously enable the test driver to support, for example, new item types, navigation algorithms, information displays, scoring algorithms, timing algorithms, test unit selection algorithms, results persistence reporting, printed score reporting, and/or helm types without change to the test driver's executable. Plugins also allow expansion of the test driver's functionality without requiring the test driver to be recompiled or re-linked, and without requiring the test publisher to learn to program. Since plugins are written independently of the test driver, plugins can be written long after the test driver is built.

The client and the software developer can design and test the plugins and distribute the plugins to each test site. By using this method, large-scale regression testing of other examinations will not usually be necessary unless changes are made to the plugins that may be used by many examinations.

A test publisher defines common plugin test specification and common plugin test content in early XXL elements. These previous elements can be referenced by later XXL elements. If the later element defines nothing more then it will receive just the common specification and content. Optionally, the later elements can define omitted non-common plugin specification and contents. Further, the later elements can override previously defined common plugin specification and contents with exception plugin specification and contents. This process of new definition and overriding of specification and contents by later XXL elements is not limited to two stages. Multiple later stages are allowed.

When a plugin delivers it uses its specification and contents to determine how and what to deliver. This will be the amalgamation of all relevant XXL elements. The amalgamation is invisible to the plugin and requires no special effort for the plugin during delivery. The amalgamation occurs at delivery time and therefore common specification and content appears only once in the compile exam resource file. Thus the size of the resource file is reduced.

I. Overview of Computer-Based Test Delivery System

FIG. 3 shows an overview of the software architecture for the computer-based test delivery system of the present invention, denoted generally by reference numeral 100. Test driver 110 is responsible for controlling all aspects of the computer-based test. Test driver 110 identifies examinees scheduled to take the computer-based test and identifies and creates the appropriate test. Test driver 110 then presents all of the test components to examinees using a display device (not shown), such as a computer monitor, and enables examinees to enter responses to test questions through the use of an input device (not shown), such as a keyboard, a mouse, etc. Test driver 110 also monitors the security of the test. For example, test driver 110 can prevent access to the Internet and can validate examinees, although, these functions are preferably performed by the test center administration system. Test driver 110 also monitors the timing of the test, providing relevant warnings to examinee regarding the elapsed time of the test and the time remaining for a particular section of the test or for the entire test. Test driver 110 is also responsible for scoring the test, once the test is completed or while the test is in progress, and for reporting the results of the test by physical printout using printer 182 or in a file format using candidate exam results file 180. If the test is interrupted while in progress, for example, due to a power failure, test driver 110 restarts the test, preferably at the point at which the test was interrupted, as will be described subsequently in more detail. Finally, if the test is left incomplete, test driver 110 cleans up the incomplete test. An incomplete test will have an exam instance file in the examinee's directory but will not have created a results file. A results file is created even though generally the candidate will fail. The number of items delivered to the examinee is recorded in the results file. Test driver 110 picks up where the event was interrupted and invisibly deliveries the rest of the units of the test.

A test specification is authored by a test publisher according to the specifications of the client and stored in exam source files 130. Exam source files 130 include data files 132, XXL files 134, multimedia files 136, and hypertext markup language (“HTML”) files 138. XXL files 134 include the test specification, which contains the client's requirements for the test, a bank of test items or questions, templates that determine the physical appearance of the test, plugins, and any additional data necessary to implement the test. Additional data is also stored in data files 132. For example an adaptive selection plugin may need a, b & c theta values. These values are stored in a binary file created by a statistical package.

HTML files 130 include, for example, any visual components of the test, such as the appearance of test items or questions, the appearance of presentations on the display device, the appearance of any client specified customizations, and/or the appearance of score reports. HTML files 130 preferably also include script, for example, VBscript and Jscript, or Java script. HTML files 130 are preferably authored using Microsoft's FrontPage 2000. FrontPage 2000 is preferably also used to manage the source files in a hierarchy that is chosen by the test publisher. Multimedia files 136 include, for example, any images (.jpg, .gif, etc.) and/or sound files (.mp3, .wav, .au, etc.) that are used during the test.

XXL compiler 140 retrieves XXL files 134 from exam source files 130 using interface 190 and compiles the XXL test content stored in XXL files 134. XXL compiler 140 stores the compiled test files in exam resource file 120. In another embodiment, exam source files 130 do not contain XXL files 134 and contains, for example, only multi-media files. In this embodiment, XXL compiler 140 is merely a test packager that writes the data directly to exam resource file 120 without modification or validation. The data appears in a stream under the “data” branch of exam resource file 120. The name of the stream is specified by the test author.

In a preferred embodiment, XXL files 134 also include XXL language that defines plugins 150, in which case, plugins 150 assist XXL compiler 140 in compiling XXL files 134. Test driver 110 preferably supports, for example, nine different types of plugins 150, including, for example: display plugin 152; helm plugin 154; item plugin 156; timer plugin 158; selection plugin 160; navigation plugin 162; scoring plugin 164; results plugin 166; and report plugin 168. Plugins 150, which are also included in XXL files 134, are the first XML files compiled into exam resource file 120.

Plugins 150 allow a test designer to customize the behavior of test driver 110 and are divided into two types, for example: visible plugins and invisible plugins, as shown in FIG. 4. The visible plugins, which include display plugin 152, helm plugin 154, and item plugin 156, enable the test driver to control what is presented visually to an examinee on the display device. The invisible plugins, which include timer plugin 158, selection plugin 160, navigation plugin 162, scoring plugin 164, results plugin 166, and report plugin 168, enable the test driver to control more functional aspects of the test. Plugins 150 are used to validate data stored in exam source files 130 that is to be used by one of plugins 150 during delivery of the test to the examinee, as is described below in greater detail. Plugins 150 are, preferably, component object model (“COM”) objects, as described below. Plugins 150, may also utilize Java implementation. Plugins 150 are preferably written using Microsoft Visual C++ or Visual Basic 6.0 or any fully COM enabled language. Plugins 150 may be in or out-of-process, and, therefore, can exist as executable (“.EXE”) files or as dynamic link library (“.DLL”) files. An application or component that uses objects provided by another component is called a client. Components are characterized by their location relative to clients. An out-of process component is an .exe file that runs in its own process, with its own thread of execution. Communication between a client and an out-of-process component is therefore called cross-process or out-of-process communication.

An in-process component, such as a .dll or .oxc file, runs in the same process as the client. it provides the fastest way of accessing objects, because property and method calls don't have to be marshaled across process boundaries. However, an in-process component must use the client's thread of execution.

Exam resource file 120 receives the compiled test content from XXL compiler 140 and plugins 150, if applicable, and stores the compiled test content in an object-linking and embedding (“OLE”) structured storage format, called POLESS, which is described in greater detail below. Other storage formats may optionally be used. OLE allows different objects to write information into the same file, for example, embedding an Excel spreadsheet inside a Word document. OLE supports two types of structures, embedding and linking. In OLE embedding, the Word document of the example is a container application and the Excel spreadsheet is an embedded object. The container application contains a copy of the embedded object and changes made to the embedded object affect only the container application. In OLE linking, the Word document of the example is the container application and the Excel spreadsheet is a linked object. The container application contains a pointer to the linked object and any changes made to the linked object change the original linked object. Any other applications that link to the linked object are also updated. POLESS supports structured storage such that only one change made to an object stored in exam resource file 120 is globally effective. Test driver 110 comprises Active Document container application 112 for the visible plugins, display plugin 152, helm plugin 154, and item plugin 156, which function as embedded objects, preferably COM objects.

FIG. 3-1 shows an example of Active Document container application 112 being used with several item plugins 156. Each item plugin 156, in this case representing a multiple choice (“multi-choice”) item, a hot area item, and a fill in the blank item, are linked to Active Document container application 112 through the IItem and IPlugin COM interfaces 169.

Both XXL compiler 140 and plugins 150 are involved in storing the compiled test content into exam resource file 120, if any of plugins 150 are being used. Exam resource file 120 comprises, for example, a hierarchical storage structure, as will be described in further detail below. Other storage structures may optionally be used. XXL compiler 140 determines to which storage location a specific segment of the compiled test content is to be stored. However, if any of plugins 150 are used to validate the portion of any of the data from exam source files 130, then the plugins 150 store the data directly to the exam resource file, based upon directions from XXL compiler 140. XXL compiler uses IPersistResource interface 192, co-located with I-Plugin interface 167 in FIG. 3, to control the persistence of the data to exam resource file 10. XXL compiler 140 and plugins 150 write the data to exam resource file 120 using POLESS interfaces 191.

FIG. 5 illustrates the contents of exam source file 130, which are compiled into exam resource file 120 by XXL compiler 140 and plugins 150. FrontPage 2000 Web 200 is used, for example, to author the test. Exam source files 130 contain media files 210, visual files 220, and logic files 230. Media files 210 are multimedia files used to enhance the presentation of the test, including, for example, XML data files 212, sound files 214, image files 216, and binary files 218. XML data files 212 include the XXL test definition language and the XXL extensions from the plugins 150 that use XML. The test specification, presentation, scoring and other information is specified in the XML files. Sound files 214 include any sounds that are to be used during the test, such as .mp3 files, .au files, etc. Image files 216 include any images to be used during the test, such as .jpg files, .gif files, etc. Binary files 218 include any data needed by a plugin 150 that is not in XXL format. Visual files 220 are HTML files that specify the visual presentation of the test as presented to the examine on the display device, including items files 222, presentation files 224, score report files 226, and custom look files 228. Items files 222 include HTML files that are used to specify the visual component of test questions, e.g., stems and distractors. Items files 222 are capable also of referencing external exhibits. An exhibit could be a chart, diagram or photograph. Formats of exhibits include, for example: .jpg, .png, etc. Presentation files 224 define what is seen by the examinee on the display device at a particular instant during the test. Score report files 226 include is typically an HTML file with embedded script that includes, for example candidate demographics, appointment information, and candidate performance. The performance might include pass/fail, achievement in different content areas, etc. Custom look files 228 include are typically HTML files with embedded script to layout, for example, the title bar and information contained therein. Logic files 230 are XML files that specify the functional aspects of the test, including test specification files 232, plugin files 234, item bank files 236, and template files 238. Test specification files 232 specify the content and progression of the test as provided by the client. Plugin files 234 define plugins 150 and contain any data necessary to implement plugins 150. Item bank files 236 include the data content and properties of the items, or test questions, that are to be presented to the examinee during the test. Properties of an item include the correct answer for the item, the weight given to the item, etc. Template files 238 define visual layouts that are used with the display screen during the test.

Referring again to FIG. 3, once a test has begun, test driver 110 accesses exam resource file 120 for the instructions and files needed to implement the test, using POLESS interfaces 193. Test driver 110 also accesses plugins 150 for additional data that expands the functionality of test driver 110 in the areas of items, navigation algorithms, information displays, scoring algorithms, timing algorithms, test unit selection algorithms, results persistence reporting, printed score reporting, and/or helm types. Test driver 110 communicates with plugins 150 using various COM interfaces 169. COM interfaces facilitate OLE linking. As stated previously, test driver 110 is an Active Document container application and plugins 150 are embedded objects. The COM interfaces function as communications paths between the container application and the objects.

There are, for example, ten COM interfaces utilized in computer-based test delivery system 100. IPlugin interface 167, which is also a COM interface, is supported by all of plugins 150. COM interfaces 169, therefore, includes the IPlugin interface. The IPlugin interface contains generic operations such as loading and unloading required of all plugins 150. In addition to the global IPlugin interface, each plugin 150 also uses, for example, a second, individual COM interface 169 to communicate with test driver 110. Alternative structures of the IPlugin interface may also be used. Table 1 shows the relationship between each plugin 150 and the COM interface 169 used with that particular plugin 150.

TABLE 1 COM INTERFACE FOR PLUGINS PLUGIN COM INTERFACE DESCRIPTION All Plugins 150 IPlugin Passes data between the test driver and all plugins regarding generic operations, e.g., loading and unloading. Display 152 IDisplay Passes data between the test driver and the visible plugins that handle title bars, displays, non-answered items, and summaries. Helm 154 IHelm Passes data between the test driver and the visible plugins that display navigation controls or reviews. Communicates with a navigation plugin to perform the actual navigation. Also functions as a user interface connection to the test driver. Item 156 IItem Passes data between the test driver and the visible plugins that govern test items or simulations. Timer 158 IUnitTimer Passes data between the test drivers and the invisible plugins used to perform timing across examination sections. Selection 160 ISelection Passes data between the test drivers and the invisible plugins used to select forms, sections, groups, or items for delivery to the examinee. Navigation 160 INavigate Passes data between the test drivers and the invisible plugins used to control section navigation and define rules for traversing through the test. Scoring 164 IScore Passes data between the test drivers and the invisible plugins used to control scoring of delivered testing units. Results 166 IResults Passes data between the test drivers and the invisible plugins that control writing of examinee results, for example, to candidate exam results file 180. Report 168 IReport Passes data between the test drivers and the invisible plugins that control printing of score reports and other material, for example, printed reference material and post exam instructions to printer 182.

Exam instance file 170 is used to restart a test if the test has been interrupted, for example, because of a power failure. During delivery of the test, exam instance file 170 receives examination state information from test driver 110 and plugins 150 regarding the state of all running objects being used to deliver the test. The examination state information includes the presentation that was being delivered on the display device before the interruption, the responses the examinee had entered in that presentation, etc. When the test is restarted, the exam instance file 170 loads the state information back to test driver 110 and plugins 150, allowing the test to return to operation at the point where the test had been interrupted. Preferably, the running state of all objects is saved to exam instance file 170 rather than of only some of the objects. Saving the state of only some of the objects to exam instance file 170 causes the potential problem of only a portion of the test information being restored after a test interruption. Exam instance file 170 may also store additional information relating to the test, including, for example: the timing utilized and time remaining on units of the exam, the current unit of delivery, candidate score, etc. Test driver 110 and plugins 150 communicate with exam instance file 170 using POLESS interfaces 195. Test driver 110 controls communications between test driver 110 and plugins 150 using IPersistInstance interface 196, which is co-located with COM interfaces 169 in FIG. 3.

Several administrative environments perform the administrative functions of computer-based test delivery system 100, for example: Test Center Manager (“TCM”) Bridge 172; Educational Testing Service (“ETS”) Bridge 174; and Unified Administration System (“UAS”) 174. Administrative functions include, for example: checking-in an examinee, starting the test, aborting the test, pausing the test, resuming the test, and transmitting results.

There are preferably two ways to run Test driver 110. The first is through a series of command line options and the second is using COM interfaces describing appointment information. The command line option exists for backwards compatibility in a standard ETS environment and a TCM environment. Table 2 shows a list of command line options test driver 110 supports. There are four programs which launch the test through the COM interface, for example: 1) LaunchTest.exe (for test production and client review); 2) UAS; 3) UTD2ETS.dll (an internal compatibility module for use with the ETS administration environment); and 4) UTD2TCM (for the Test Center Manger environment). Other number of environments and/or programs may optionally be used.

Switch(es) Option(s) Purpose /?/help n/a Displays command line switches in dialog box. /UnregServer n/a Unregisters the test driver core COM server. /Regserver n/a Registers the test driver core COM server. /T form name Name of the form or form group to run in the exam. /F resource The exam resource file to use. file /S n/a Suppress any printing. /W n/a Run in close-of-day mode. /TI n/a Set tracing level to information. (Very large instance file). /TW n/a Set tracing level to warning. (Large instance file.) /TE n/a Set tracing level to error. (Average sized instance file.) /K resource Used to point to directories. A space dir, SKSID, separates each of the three options. candidate director

The administration environments use several interfaces to communicate with test driver 110. IAppointment interface 176 is part of UAS 174 and allows access by test driver 110 to examinee information for the examinee taking the test, such as demographics. The examinee information is included in candidate exam results file 180, which is created by the test driver. ILaunch2 interface 177 functions as the primary control interface for UAS 174 and allows UAS 174 to control various components such as test driver 110, screen resolution change, accommodations for disabled candidates, examinee check-in, etc., in a test center, which is the physical location where the examinee is taking the test. ITransfer interface 199 transfers candidate exam results file 180 and other files back to UAS 174. IPrint interface 198 sends information regarding any reports to printer 182.

II. XXL Compiler Interfaces and Classes

FIGS. 6A and 6B illustrate the main diagram for XXL compiler 140. XXL compiler 140 comprises the following classes, for example: cCompile 2000; cData 2004; cArea 2006; cTemplate 2008; cCategory 2010; cItem 2012; cPresentation 2014; cGroup 2016; cSection 2018; cForm 2020; cFromGroup 2022; cExam 2024; cMsgBox 2026; cChecksum 2028; cEvent 2030; cResult 2032; cReport 2024; cPlugin 2036; and cXXL 2038.

The main interface to XXL compiler 140 is ICompile interface 2002. ICompile interface 2002 is implemented by cCompiler class 2000. All control and initiation of compilation of exam source files 130 into exam resource file 120 occurs by way of this single public interface. The core, non-plugin related elements of the XXL test definition language, as stored in XXL files 134, are compiled by classes in XXL compiler 140. For example, cSection class 2018, compiles the section element, and cGroup class 2016 compiles the group element.

ICompile interface 2002 supports the following operations, for example: createResource( ); addSource( ); addData( ); closeResource( ); about( ); linkResource( ); openResource( ) and getCryptoObject( ). CreateResource( ) creates a resource file, for example, an XXL based resource file such as exam resource file 120. AddSource( ) compiles an XXL file into the resource file. AddData( ) adds a file directly to a data branch of the resource file. CloseResource( ) closes the resource file. LinkResource( ) links a resource in the resource file and is performed after all compiling of the source files are completed. GetCryptoObject( ) returns an ICrypto object containing the current encryption setting of POLESS, as described below.

The classes of XXL compiler 1040, e.g., cForm 2020 and cItem 2012, handle individual XXL core language elements. All of these classes compile the specific XXL source element into exam resource file 120. All of these class language elements are also symbols used in later references. Therefore, the classes all derive from cSymbol class 2040. cSymbol class 2040 allows the classes of XXL compiler 140 to reside in a symbol table.

For example, the XXL element plugin 150 appears as follows in XXL files 134:

<plugin name=“helmNextPrevious”

progid=“UTDP.cNextPrevious”/>

This XXL call causes an instance of cPlugin class 2036 to be created, compiles the source, and writes the compiled result to exam resource file 120. The name and ID of Plugin 150 is also added to the symbol table for later reference.

XXL compiler 140 also contains the following token classes, for example: cToken 2042; cTokenCreatorNoRef 2044; cTokenCreator 2046; CtokenCreatorRef 2048; cTokenCreatorBase 2050; and cTokenFactory 2054. These token classes are involved in the identification of tokens. Tokens turn into symbols after identification. Symbols are any class derived from cSymbol, e.g., cTemplate, cSection, etc.

XXL compiler 140 also contains the following symbol table classes, for example: cPluginSymbolTable 2058; cTemplateSymbolTable 2060; cSymbolTable 2062; cFFGSymbolTable 2064; cSGPSymbolTable 2066; and cSymbolTableBase 2068. These classes are varieties of symbol tables. There are different symbol tables for different groups of symbols. A group of symbols define a name space for the symbol. Common symbol table functions are located in the base symbol table classes and templates.

All content and specification destined for a plugin 150 appears in the data element in XXL. For example, below is an item definition in XXL:

<item name=“wantABreak1” skipAllowed=“false”>   <data>     <multiChoice       correctAnswer=“A”       maxResponses=“1”       minResponses=“1”       autoPrompt=“false”       URI=“itembank/info_item.htm#wantABreak”/>   </data> </item> The item element is handled by a cItem class 2012 object. The data element in the XXL definition is handled by a cData class 2004 object. Item plugin 156 Plugin 150 will receive the source to compile from the cData class 2004 object, in this example, a multiChoice element.

cWrapXML class 2052, a wrapper class for XML DOM nodes, supports error handling. cCustomAttributes class 2056 compiles the custom attributes XXL element. cWrapPropertySet class 2070 is a wrapper class for a POLESS property storage.

III. Test Driver Interfaces and Classes

A. Interfaces

FIG. 7 shows test driver 110, UAS 174, and the interfaces used by and between the test driver 110 and UAS 174 to deliver the test. UAS 174 defines ILaunch2 interface 177, which is used by UAS 174 to initiate test events. ILaunch2 interface 177 is an extension of ILaunch interface 178, which, in other embodiments of the present invention, is also used by UAS 174 to initiate test events. UAS 174 also defines and implements additional interfaces, for example: IAppointment interface 176; IPrint interface 198; and ITransfer interface 199. IAppointment interface 176 transfers examinee candidate information and appointment details from UAS 174 to test driver 110, as is illustrated by the dashed arrow connecting IAppointment interface 176 to test driver 110. IPrint interface 198 allows UAS 174 to send print requests to printer 198 regarding reports, for example, score reports. ITransfer interface 199 allows UAS 174 to request the transfer of information from candidate exam results file 180 back to UAS 174.

Test driver 110 defines various interfaces to allow test driver 110 to communicate with different parts of computer-based test delivery system 100. Test driver 110 includes, for example, ten COM interfaces 169 to communicate and transfer data with plugins 150. (See Table 1 above) The COM interfaces 169 are denoted in FIG. 7 as follows, for example: IDisplay interface 169 a; IHelm interface 169 b; IItem interface 169 c; IUnitTimer interface 169 d; ISelection interface 169 e; INavigate interface 169 f; IScore interface 169 g; IResults interface 169 h; IReport interface 169 i; and IPlugin interface 169 j.

Test driver 110 and plugins 150 communicate and transfer data with exam resource file 120 using, for example, three IPersistResource interfaces 192: IPersistResourceStream interface 192 a; IPersistResourceSet interface 192 b; and IPersistResourceStore interface 192. IPersistResource interfaces 192 are used by plugins 150 during compilation of exam source files 130 and are used by both test driver 110 and plugins 150 during delivery of the test. During compilation of exam source files 130, XXL compiler 140 directs plugins 150 in which storage location of exam resource file 120 to store any information that plugins 150 have validated. Plugins 150 can then retrieve the stored information from exam resource file 150 during delivery of the test. Other number of interfaces and different combination of functionality may alternatively be used.

Information is saved from plugins 150, or from XXL compiler 140 in general, to exam resource file 120, for example, as either a stream of data, as a set of data, or as a storage structure, depending on which of the three IPersistResource interfaces 192 is implemented to save the information from plugins 150, to exam resource file 120. IPersistResourceStream interface 192 a saves the information, for example, as a stream of data. A stream of data is simply a stream of bytes stored as a linear sequence. IPersistResourceSet interface 192 b saves the information, for example, as a set of data. A set of data is preferably a name-value property pair. For example, the name of a particular property for an item is distractors and the value is the number of distractors required for that item. IPersistResourceSet interface 192 allows the name-value property pair to be saved together in exam resource file 120. IPersistResourceStore interface 192 c saves the information, for example, in a directory format with storage areas. The directory format allows other streams of data to be saved within the storage area and for sub-storages to be saved under the storage area.

IPersistInstance interface 196, likewise, comprises, for example, three, different interfaces, for example: IPersistInstanceStream interface 196 a; IPersistInstanceSet interface 196 b; and IPersistInstanceStore interface 196 c. Examination state information is saved to exam instance file 170 as, for example, a stream of data, as a set of data, or as a storage element, depending on which of the three IPersistResource interfaces 192 is implemented.

Two of the interfaces, IContainerNotify interface 200 and IContainerNotifyHelm interface 206, function as callback interfaces from plugins 150 to test driver 110. IContainerNotify interface 200 allows a visible plugin to inform test driver 110, for example, that the plugin is displayed and ready for examinee interaction. IContainerNotifyHelm interface 206 allows helm plugin 154 to request navigation from test driver 110 after receiving an input from the examinee to move to another section of the test. IMore interface 202 is used to convey whether the examinee has seen all content in a presentation. For example, a “more” button appears in place of the next button when the content exceeds the window length. When the examinee scrolls to the bottom, the “more” button disappears and is replaced with the “next” button. Collection interface 204 is used by test driver 110 to hold any group entities, for example, categories and sections of the test.

The remaining interfaces are, for example, Microsoft defined Active Document interfaces, used to implement OLE linking functions of test driver 110 and the visible plugins, display plugin 152, helm plugin 154, and item plugin 156. IOleInPlaceFrame interface 210 controls the container's top-level frame window, which involves allowing the container to insert its menu group into the composite menu, install the composite menu into the appropriate window frame, and remove the container's menu elements from the composite menu. IOleInPlaceFrame interface 210 sets and displays status text relevant to the end-place object. IOleInPlaceFrame interface 210 also enables or disables the frames modeless dialogue boxes, and translates accelerator key strokes intended for the container's frame. IOleInPlaceUI window interface 211 is implemented by container applications and used by object applications to negotiate boarder space on the document or frame window. The container provides a RECT structure in which the object can place toolbars and other similar controls, determine if tools can in fact be installed around the objects' window frame, allocates space for the boarder, and establishes a communication channel between the object and each frame and document window. IAdviseSync interface 212 enables containers and other objects to receive notifications of data changes, view changes, and compound-document changes occurring in objects of interest. Container applications, for example, require such notifications to keep cached presentations of their linked and embedded objects up-to-date.

Calls to IAdviseSync interface 212 methods are a synchronous, so the call is sent and then the next instruction is executed without waiting for the calls return. IOleWindow interface 213 provides methods that allow an application to obtain the handle to the various windows that participate in-place activation, and also to enter and exit context-sensitive help mode. IOleInPlaceSite interface 214 manages interaction between the container and the objects in-place client site. The client site is the display site for embedded objects, and provides position and conceptual information about the object. IOleClientSite interface 215 is the primary means by which an embedded object obtains information about the location and extent of its display site, its moniker, its user interface, and other resources provided by its container. Test driver 110 called IOleClientSite interface 215 to request services from the container. A container must provide one instance of IOleClientSite interface 215 for every compound-document it contains. IOleDocumentSite interface 216 enables a document that has been implemented as a document object to bypass the normal activation sequence for in-place-active objects and to directly instruct its client site to activate it as a document object. A client site with this ability is called a “document site”.

B. Core Classes

FIGS. 8A and 8B illustrate the main classes of test driver 110 and the interfaces between test driver 110 and plugins 150. Also shown are the classes that interface to UAS 174. ITransfer interface 199, IPrint interface 198, ILaunch2 interface 177, and IAppointment interface 176 represent the connections from test driver 110 to UAS 174, as described previously. Some of the lines depicted in FIG. 8 are solid and some are dashed. The solid lines, for example, between IcResults interface 240 and cEvent class 252, represent inheritance. The dashed lines, for example, between IExam interface 222 and IPlugin interface 169 j, represent instantiation.

Inheritance, or generalization, relates to a generalized relationship between classes that shows that the subclass shares the structure or behavior defined in one or more superclasses. A generalized relationship is a solid line with an arrowhead pointing to the superclass. Instantiation, or dependency, represents a relationship between two classes, or between a class and an interface, to show that the client class depends on the supplier class/interface to provide certain services. The arrowhead points to the supplier class/interface. Some services from a supplier class to a client class include, for example: the client class access a value (constant or variable) defined in the supplier class/interface; methods of the cline class invoke methods of the supplier class/interface; and methods of the client class have signatures whose return class or arguments are instances of the supplier class/interface. For instantiation, the cardinality of the relationship is illustrated in FIG. 8 if the relationship represents containment. Cardinality specifies how many instances of one class may be associated with a single instance of another class. Cardinality can be shown for relationships to indicate the number of links allowed between one instance of a class and the instances of another class.

Test driver 110 also has several interfaces and implementing classes. Test driver 110 interfaces include, for example: IExam interface 222; IMsgBox interface 224; ICategory interface 232; IForm interface 238; IcResults interface 240; IcReport interface 242; IScript interface 246; ISection interface 250; IPresentation interface 248; and/or IcItem interface 256. The classes that implement the main interfaces include, for example: cScreenMinimum class 226; cFormGroup class 228; cPlugin class 230; cArea class 234; cTemplate class 236; cActivePlugin class 250; and cEvent class 252. The interfaces that are prefaced by “Ic” have names that already exist for plugins 150 to enact, for example, item plugin 156 implements IItem interface 169 c. IcItem interface 256, however, is the interface implemented by test driver 110 class cItem (not shown). Of course, any number of interfaces may be used, depending on the necessary functionality.

The core class cExam (not shown) implements ILaunch2 interface 177 so that UAS 174 can control test driver 110. The appointment object, which implements IAppointment interface 176, is the main object UAS 174 supplies to test driver 110. The appointment object is available to plugins 150 by way of IPlugin interface 169 j. Furthermore, all plugins 150 get access to the test (Iexam) using the IPlugin interface 169, also.

The cExam class selects and delivers the form, using cFormGroup class 228 and IForm interface 238. The form delivers results using IcResults interface 240, reports using IcReport interface 242, and sections contained with in the test using ISection interface 250. Classes that are in the test delivery chain preferably derive from cEvent class 252.

The cResults class (not shown) delivers a results plugin 166 that implements IResult interface 169 i. The cReport class (not shown) delivers a report plugin 168 that implements IReport interface 169 h. The cSection, cGroup, and cForm classes (not shown) use several invisible plugins 150 to control the delivery of the test. These plugins 150 are timer plugins 158, which implement IUnitTimer interface 169 d, selection plugins 160, which implement ISelection interface 169 e, scoring plugins 164, which implement IScore interface 169 g, and navigation plugins 162, which implement INavigate interface 169 f. The cPresentation class (not shown) supplies data to its template for the display of the presentation. The three visible plugins 150 are created and controlled through cTemplate class 236 and child objects cArea class 234. Item plugins 156 have an extension class in the cItem class (not shown) that wraps the item plugin 156 and provides generic extended services that all item plugins 156 implements. The cItem class in test driver 110 is a wrapper class. The cItem class provides two base services, for example: generic item functionality and access to item plugin 156, which is the wrapping function. Item generic functionality includes, for example: having an item name, having an item title, determining if the item is scored or un-scored, determining whether the item has been presented to the examinee, etc. These services are generic to all items and are provided by test driver 110. Item plugins 156 perform the actual scoring of the item, which is unique to each item type. Item plugins 156 present the content of the item and allow the examinee to interact with the item. These services are unique to each item type.

In addition to the interfaces described previously, test driver 110 implements IRegistry interface 220, which allows VB code to access the Windows registry. Test driver 110 also implements ILegacyItem interface 258 and ILegacyScore interface 260, which are defined by test driver 110 and are implements by certain item plugins 156 and scoring plugins 164. ILegacyItem interface 258 and ILegacyScore interface 260 allow old item types that existed in previous test drivers to report results like the previous test drivers. For some tests, test driver 110 must report results for old item types, which had very specific ways of reporting results. ILegacyItem interface 258 and ILegacyScore interface 260 allow the new item plugins 156 that represent old item types to report this legacy format of information to result plugins 166 trying to imitate previous test drivers.

A complete description of test driver 110 classes and interfaces is included in Appendix A.

IV. POLESS

All persistent storages, exam resource file 120 and exam instance file 170, preferably utilize POLESS. POLESS allows data to be embedded, linked, or references as external files from the persistent storage to test driver 110 and Active Document container application 112 (FIG. 3). POLESS supports a hierarchical tree structure with node or branch level additions, replacements, and deletions. POLESS also supports optional data encryption at the node level. The type of encryption employed depends on the destination of the information in the persistent storage. For example, different encryption keys may optionally be used for data being routed to test centers, data being routed to administrative data centers, and data being routed for client use (e.g., client review). Microsoft Crypto-API is preferably used to perform encryption of data in the persistent storage. Finally, POLESS also supports optional compression at the node level, preferably using Lempal-Zev compression.

POLESS is an extension of OLE structured storage compound document implementation. A compound document is a single document that contains a combination of data structures such as text, graphics, spreadsheets, sound and video clips. The document may embed the additional data types or reference external files by pointers of some kind. There are several benefits to structured storage. Structured storage provides file and data persistence by treating a single file as a structured collection of objects known as storage elements and streams. Another benefit is incremental access. If test driver 110 or plugins 150 need access to an object within a compound file, only that particular object need be loaded and saved, rather than the entire file. Additionally, structure storage supports transaction processing. Test driver 110 or plugins 150 can read or write to compound files in transacted mode, where changes made can subsequently be committed or reverted.

A. POLESS Components

FIG. 9 shows the major components that support POLESS and the interfaces that connect the components. POLESS 300 may be either exam resource file 120 or exam instance file 170. POLESS 300 utilizes PKware library component 330 for storage compression and decompression. POLESS 300 uses Crypto API component 332, a Microsoft application, for storage encryption and decryption. Crypto API component 332 relies on a crypto service provided (“CSP”) 334 to perform the actual encryption algorithms. Access to the services of these components is facilitated by standard (API) interfaces exposed by these components.

OLE2SS component 310 contains all the interface definition that makeup structure storage. These interfaces can be realized by any structured storage implementation, such as compound document implementation OLE2 320 and POLESS 300. The interfaces include, for example: IStream interface 340; ISequentialStreath interface 342; IStorage interface 344; and IRootstorage interface 346. POLESS 300 additionally implements IStreamVB interface 348 and IStorageVB interface 350.

IStreamVB interface 348 supports several functions, for example: ReadVB( ); WriteVB( ); Clear( ); Reset( ); get_sName( ); get_oStream( ); and CopyTo( ). ReadVB( ) reads a specified number of bytes to a data array. WriteVB( ) writes the byte data to the stream. Clear( ) clears the stream of all data. Reset( ) sets position to the beginning of the stream. get_sName( ) is a read-only function that returns the name of the stream. get_oStream( ) is a read-only function that returns the IStream interface 348. CopyTo( ) copies a source stream to a destination stream.

IStorageVB interface 350 supports several functions, for example: Clear( ); CommittVB( ); RevertVB( ); sElementName( ); bStorage( ); oElement( ); CreateStream( ); OpenStream( ); CreateStorage( ); OpenStorage( ); get_sName( ); get_oStorage( ); get_nCount( ); GetCompression( ); GetEncryption( ); GetCRC( ); CreateStreamLinked( ); CreatePropertyStg( ); OpenPropertyStg( ); SetClass( ); RegisterAlias( ); Destroy( ); and get_ElementType( ). Clear( ) clears the storage of all elements. CommittVB( ) causes transacted mode changes to be reflected in the parent. RevertVB( ) discards changes made since the last commit. sElementName( ) returns the name of the element. bStorage( ) returns TRUE if the element is a sub-storage. oElement( ) returns IStreamVB interface 348 or IStorage interface VB 350 for the element. CreateStream( ) creates and opens a stream and returns IStreamVB interface 348.

OpenStream( ) opens a stream and returns IStreamVB interface 348. CreateStorage( ) creates and opens a nested storage and returns IStreamVB interface 348. OpenStorage( ) opens an existing storage and returns IStreamVB interface 348. get_sName( ) is a read-only function that returns the name of the storage. get_oStorage( ) is a read-only function that returns IStorage interface 350. get_nCount( ) is a read-only function that returns a count of the elements. GetCompression( ) returns the status of file compression. GetEncryption( ) returns the status of file encryption. GetCRC( ) return the status of file CRC checking. CreateStreamLinked( ) creates and opens a linked stream and returns IStreamVB interface 348. CreatePropertyStg( ) creates and opens a property storage and returns IpropertyStorageVB interface 414. OpenPropertyStg( ) opens a property storage and returns IpropertyStorageVB interface 414. SetClass( ) sets the CLSID for the storage. RegisterAlias( ) registers a pluggable protocol. Destroy( ) destroys the specified elements. get_ElementType( ) is a read-only function that returns the type of the element.

B. POLESS Classes

FIG. 10 shows the main class of POLESS 300, the interfaces used to implement the classes, and the flow of the creation of streams 424 and storages 426. cFileRoot class 400 is the first object instantiated and is used to create a new or open an existing a POLESS file. cStorageRoot class 406 is returned, which is a slightly overloaded version of cStorage class 410. From cStorageRoot class 406 creates or opens cStream class 408 and cStorage class 410, from which any streams or storages and sub-storages of those can be created or opened, respectively. For instance, cStorage class 410 creates cPropertyStorage class 412, which creates storage for property sets. The classes implement interfaces that perform operations and/or define attributes that further define the function or properties of the class. A complete description of POLESS 300 classes and interfaces is included in Appendix B.

1) cFileRoot Class

cFileRoot class 400 is the root POLESS class and controls the creation and opening of all POLESS files. cFileRoot class 400 is generally instantiated first before any other POLESS objects can be created, although other sequences are possible. cFileRoot class 400 implements IFileRoot interface 401, which is collocated in FIG. 10 with cFileRoot class 400. IFileRoot interface 401 is used to open one file at a time and is not released until all other storage object 426, stream object 424, and property storage interfaces are released and the file, is ready to be closed. cFileRoot class 400 and IRoot interface support the following operations, for example: StorageFileCreate( ); StorageFileOpen( ); CryptoGet( ); bStorageFile( ); StorageAmalgamatedGet( ); DeltaFileCreate( ); DeltaFileApply( ); GetObjectFromPath( ); CreateStreamFromBSTR( ); MemoryStreamFromStream( ); GetPicture( ); and SavePicture( ).

StorageFileCreate( ) creates a new storage file, returns the root storage to interface, marks the new structured storage file as a POLESS file by storing the class ID (“CLSID”) of this class in a stream in the root storage. StorageFileOpen( ) opens an existing storage file and returns the root storage interface. CryptoGet( ) gets a default configured crypto class and should be set and used on the open or create of the storage file. bStorageFile( ) returns true if the file provided is an OLLE structured storage file and not a POLESS storage file. StorageAmalgamatedGet( ) gets an empty small cStorageAmalgamated class 404. DeltaFileCreate( ) creates a POLESS difference file by comparing the original POLESS file to the updated POLESS file. DeltaFileApply( ) applies a POLESS delta file and applies the original POLESS file to the delta file to create an updated POLESS file. GetObjectFromPath( ) uses monikers to retrieve the object named by the path and returns a pointer to the object retrieved. CreateStreamFromFile( ) creates a structured storage stream and populates it with the contents of the file. CreateStreamFromBSTR( ) creates a structures storage stream and fills it with the specified string. MemoryStreamFromStream( ) is used to copy a stream to a newly created memory stream object. GetPicture( ) loads a picture from stream object 424. SavePicture( ) saves the picture into the stream 426.

2) cCrypto Class

cCrypto class 402 controls the configuration of the encryption/decryption of POLESS 300. cCrypto class 402 has the following attributes, for example: sProviderName; eProviderType; sContainerName; and sPassword. SProviderName represents the name of CSP 334 being used to perform the encryption/decryption services. eProviderType is the type of CSP 334. The field of cryptography is large and growing. There are many different standard data formats and protocols. These are generally organized into groups or families, each of which has its own set of data formats and way of doing things. Even if two families used the same algorithm, for example, the RC2 block cipher, they would often use different padding schemes, different key links, and different default modes. Crypto API is designed so that a CSP provider type represents a particular family. sContainerName is the key name and must be provided by cCrypto class 402. sPassword is an optional password on the public/private key pair and can only be entered by a human operator. The password can be used for review disks and their resource files.

cCrypto class 402 implements ICrypto interface 401 and they support the following properties and method, for example: ProviderName; Password; FileType; Algorithm; EnumProviders( ); and EnumAlgorithms( ). Get_ProviderName( ) returns the name of the Crypto provider. Put_ProviderName( ) sets the name of the Crypto provider. Get_Password( ) and Put_Password( ) are only used for sponsor resource files. Get_FileType( ) gets the file type and put_FileType( ) sets the file type. Get_Algorithm( ) gets the encryption algorithm and put_Algorithm( ) sets the encryption algorithm. EnumProviders( ) returns an enumerator for the list of installed providers. EnumAlgorithms( ) enumerate a list of algorithms for the current provider.

3) cStorageAmalgamated Class

cStorageAmalgamated class 404 is an implementation of IStorage interface 344. cStorageAmalgamated class 404 holds references to an ordered collection of IStorage objects. When a stream is opened, cStorageAmagalmated class 404 searches the collection of storage objects in order to find the first storage object that has the requested stream and returns this stream. cStorageAmalgamated class 404 handles compound storage resolution and delegates all other work to cStorage class 410. cStorageAmalgamated class 404 is, for example, read-only. cStorageAmalgamated class 404 will not allow stream or storages to be created but is primarily for reading exam resource file 120. cStorageAmalgamated class 404 implements IStorageAmalgamated interface 405. cStorageAmalgamated class 404 and IStorageAmalgamated interface 405 support the following operations, for example: StorageAdd( ); Clearstorage( ); OpenStorageAmalgamated( ); and OpenPropertyStgAmalgamated( ). StorageAdd( ) adds a new storage to the collection of storages. Clearstorage( ) clears all the storage objects from the collection. OpenStorageAmalgamated( ) opens a sub-storage of the current amalgamated storages in an amalgamated fashion. OpenPropertyStgAmalgamated( ) opens a property storage of the current amalgamated storages in an amalgamated fashion. Amalgamation is described in greater detail, in the co-pending application filed on the same date, entitled “EXTENSIBLE EXAM LANGUAGE (XXL) PROTOCOL FOR COMPUTER BASED TESTING,” incorporated herein by reference.

4) cStorageRoot Class

cStorageRoot class 406 is the POLESS implementation of IStorage interface 344 and IRootstorage interface 346. cStorageRoot class 406 handles any storage object 426 that is POLESS specific and then delegates work to the cStorage class 410. IRootstorage interface 346 supports the SwitchToFile( ) operation, which copies the current file associated with the storage object to a new file, which is then used for the storage object and any uncommitted changes. cStorageRoot class 406 also implements IPersistFile interface 418, which provides methods that permit an object to be loaded from or saved to a disk file, rather than a storage object or stream. Because the information needed to open a file varies greatly from one application to another, the implementation of IPersistFile::Load on the object preferably also open its disk file. IPersistFile interface 418 inherits its definition from IPersist, so all implementations must also include the GetClassID( ) method of IPersist interface 418.

5) cStream Class

cStream class 408 is the POLESS implementation of IStream interface 340. cStream class 408 handles any storage object 426 that is POLESS specific and then delegates work to compound document implementation OLE2 320. The specific work includes compression/decompression and encryption/decryption of stream object 424.

IStream interface 340 supports the following operations, for example: Seek( ); SetSize( ); CopyTo( ); Committ( ); Revert( ); LockRegion( ); UnlockRegion( ); Stat( ); and Clone( ). Seek( ) changes the seek pointer to a new location relative to the beginning of stream object 424, the end of stream object 424, or the current seek pointer. SetSize( ) changes the size of stream object 424. CopyTo( ) Copies a specified number of bytes from the current seek pointer in stream object 424 to the current seek pointer in another stream object 424. Commit( ) ensures that any changes made to a stream object 424 open in transacted mode are reflected in the parent storage object. Revert( ) discards all changes that have been made to a transacted stream since the last call to IStream::Commit. LockRegion( ) restricts access to a specified range of bytes in stream object 424. Supporting this functionality is optional since some file systems do not provide this operation. UnlockRegion( ) removes the access restriction on a range of bytes previously restricted with IStream::LockRegion. Stat( ) retrieves the STATSTG structure for the stream object 424. Clone( ) creates a new stream object that references the same bytes as the original stream but provides a separate seek pointer to those bytes.

IStreamVB interface 348 is an automation friendly version of IStream interface 340. IStreamVB interface 348 supports the following operations, for example: Read( ); Write( ); Clear( ); Reset( ); get_sName( ); get_oStream; and CopyTo( ). Read( ) reads data from stream object 424. Write( ) writes data, including the entire byte array, to stream object 424. Clear( ) clears stream object 424 of all data. Reset( ) resets the position in stream object 424 to the beginning of stream object 424. Get_sName( ) returns the name of the stream. Get_oStream( ) returns the IDispatch interface. CopyTo( ) copies the contents of a source stream to a destination stream.

6) cStorage Class

cStorage class 410 is the POLESS implementation of IStorage interface 344 and IcStorage interface 411. cStorage class 410 handles any storage object 426 that is POLESS specific and then delegates work to compound document implementation OLE2 320.

IStorage interface 344 supports the following operations, for example: CreateStream( ); OpenStream( ); CreateStorage( ); OpenStorage( ); CopyTo( ); MoveElementTo( ); Commit( ); Revert( ); EnumElements( ); DestroyElement( ); RenameElement( ); SetElementTimes( ); SetClass( ); SetStateBits( ); and Stat( ). CreateStream( ) creates and opens a stream object 424 with the specified name contained in a storage object. OpenStream( ) opens an existing stream object 42A within a storage object using specified access permissions. CreateStorage( ) creates and opens a new stream object 424 within a storage object. OpenStorage( ) opens an existing storage object 426 with the specified name according to the specified access mode. CopyTo( ) copies the entire contents of an open storage object 426 into another storage object. The layout of the destination storage object may differ from the layout of the source storage object. MoveElementTo( ) copies or moves a sub-storage or stream object 424 from one storage object 426 to another storage object.

Commit( ) reflects changes for a transacted storage object 426 to the parent level. Revert( ) discards all changes that have been made to the storage object 426 since the last IStorage::Commit operation. EnumElements( ) returns an enumerator object that can be used to enumerate storage objects 426 and stream objects 424 contained within a storage object. DestroyElement( ) removes the specified storage object 426 or stream object 424 from a storage object. RenameElement( ) renames the specified storage object 426 or stream object 424 in a storage object. SetElementTimes( ) sets the modification, access, and creation times of the indicated storage element, if supported by the underlying file system. SetClass( ) assigns the specified CLSID to a storage object. SetStateBits( ) stores state information in a storage object, for example up to 32 bits. Stat( ) returns the STATSTG structure for an open storage object.

IStorageVB interface 350 is an automation friendly version of IStorage interface 344. IStorageVB interface 350 supports the following operations, for example: Clear( ) Commit( ) Revert( ) sElementName( ) bstorage( ) bElement( ) CreateStream( ) OpenStream( ) Createstorage( ) Openstorage( ) get_sName( ) getoStorage( ) get_nCount( ) GetCompression( ) GetEncryption( ) GetCRC( ) CreateStreamLinked( ) CreatePropertyStg( ) OpenPropertyStg( ) SetClass( ) RegisterAlias( ) Destroy( ) and get_ElementType( ) Clear( ) clears the storage of all elements, e.g. sub-storages and streams. Commit( ) ensures that any changes made to a storage object opened in transacted mode are reflected in the parent storage. For non-root storage objects in direct mode, this method has no effect. For a root storage, it reflects the changes in the actual device, for example, a file on disk. For a root storage object open in direct mode, the commit( ) method is always called prior to releasing the object. Commit( ) flushes all memory buffers to the disk for a root storage in direct mode and will return an error code upon failure. Although releasing the object also flushes memory buffers to disk, it has no capacity to return any error codes upon failure. Therefore, calling releasing without first calling commit( ) causes indeterminate results. Revert( ) discards all changes that have been made to the storage object since the last Commit( ) operation.

sElement( ) returns the name of the element. bstorage( ) returns true if the element is a sub-storage. bElement( ) returns either iStreamVB interface 412 or iStreamVB interface 414 or IStorageVB interface 412 for the selected element. CreateStream( ) creates and opens a stream object with the specified name contained in the storage object. Nothing is returned if the stream cannot be created. OpenStream( ) opens an existing stream object within this storage object in the specified access mode. Nothing is returned if the stream cannot be opened. Createstorage( ) creates and opens a new storage object nested within the storage object. Nothing is returned if the storage cannot be created. Openstorage( ) opens an existing storage object with a specified name in the specified access mode. Nothing is returned if the storage cannot be opened. Get_sName( ) returns the name of the storage. Get_oStorage( ) returns the IDispatch interface, which exposes objects, methods and properties to programming tools and other applications that support Automation. COM components implement the IDispatch interface to enable access by Automation clients, such as Visual Basic.

Get_nCount( ) returns the count of elements in the storage. GetCompression( ) determines if streams may be compressed in the file and if enabled streams may optionally be compressed when created. GetCRC( ) indicates whether a cyclic-redundancy-check (“CRC”), or a digital signature, check is to be performed on the file. CreateStreamLinked( ) creates a link to a stream in another POLESS file. CreatePropertyStg( ) creates a property storage. OpenPropertyStg( ) opens a property storage. SetClass( ) assigns the specified CLSID to a storage object. RegisterAlias( ) registers an alias to a storage in the POLESS file for access by the pluggable protocol. Destroy( ) destroys the specified element. Get_ElementType( ) is a read-only command that returns the type of the element.

7) cPropertyStorage Class

cPropertyStorage class 412 implements IPropertyStorage interface 413, which supports the following operations, for example: ReadMultiple( ); WriteMultiple( ); DeleteMultiple( ); ReadPropertyNames( ); WritePropertyNames( ); DeletePropertyNames( ); SetClass( ); Commit( ); Revert( ); Enum( ); Stat( ); and SetTimes( ); ReadMultiple( ); reads property values in a property set. WriteMultiple( ) writes property values in a property set. DeleteMultiple( ) deletes property values in a property set. ReadPropertyNames( ) gets corresponding strung names fro given property identifiers. WritePropertyNames( ) creates or changes string names corresponding to given property identifiers. DeletePropertyNames( ) deletes string names for given property identifiers. SetClass( ) assigns a CLSID to a property set. Commit( ) flushes or commits changes to a property storage object, as is done with the command IStorage::Commit, described previously. Revert( ) discards all changes made since the last commit call when a property storage is opened in transacted mode. Enum( ) creates and gets a pointer to an enumerator for properties within a property set. Stat( ) receives statistics about a property set. SetTimes( ) sets modification, creation, and access times for a property set.

IPropertyStorageVB interface 414 is an automation friendly version of IPropertyStorage interface 413 that manages the persistent properties of a single property set. IPropertyStrorageVB interface 414 supports the following operations, for example: ReadVB( ); WriteVB( ); Delete( ); CommitVB( ); RevertVB( ); SetClass( ); get_nCount( ); CopyTo( ); GetName( ); WriteMultiple( ); and ReadMultiple( ); ReadVB( ); reads the value of a specified property from the property set. WriteVB( ) writes a value for a specified property to the property set. If the property does not exist the property/value pair will be created. If the property already exists, the value will be updated if opened in eAccess_Write mode. Delete( ) removes a property from the property set. CommitVB( ) lushes or commits changes to a property storage object, as is done with the command IStorage::Commit, described previously. RevertVB( ) discards all changes made since the last commit call when a property storage is opened in transacted mode. SetClass( ) assigns the specified CLSID to a property storage object. Get_nCount( ) returns the count of properties in the property set. CopyTo( ) copies the contents of the source property set to, a destination property set. GetName( ) returns the name of the specified property. WriteMultiple( ) rites property values in a property set. ReadMultiple( ) eads property values in a property set.

8) cPropertyStorageAmalgamated Class

cPropertyStorageAmalgamated class 416 implements IPropertyStorageAmalgamated interface 417, which supports the following operations, for example: PropertyStorageAdd( ) and ClearStorage( ). PropertyStorageAdd( ) adds a property set to the collection of property sets. ClearStorage( ) clears the collection of property sets.

C. POLESS Exam Resource File

FIGS. G and H1-H14 illustrate the POLESS layout of exam resource file 120 according to the present invention. Exam resource file 120 stores the various pieces of compiled information from exam source files 130, as shown in FIG. 5. Exam resource file 120 contains all of the content required to deliver the test. However, where the test is media-intense, exam resource file 120 will contain the core elements for the test with “links” to the external content. XXL compiler 140 and plugins 150 store the compiled information to exam instance file 120 using one of IPersistResourceStream interface 192 a, IPersistResourceSet interface 192 b, or IPersistResourceStore interface 192 to store the compiled information as a stream of data, a set of data, or a storage element, respectively. In a preferred embodiment, the layout of exam resource file 120 is in a hierarchical POLESS format that directly implements the format of the XXL test definition language. The test developer uses the XXL test definition language to create the logic files 230 and data files 212 (FIG. 5) of exam source file 130. By having a storage structure that follows the format of the XXL test definition language, the incremental access aspect of POLESS is easily implemented. XXL compiler 140 determines the storage location in exam resource file 120 that stores a particular piece of compiled information, even information stored into exam resource file 120 by one of plugins 150.

FIG. 11 illustrates the main storage branches of exam resource file 120, which corresponds to the top-level elements of the XXL test definition language, denoted by reference numeral 500. The main storage branches of exam resource file 120 are, for example: exams branch 550; forms branch 600; items branch 650; category branch 700; templates branch 750; sections branch 800; groups branch 850; plugins branch 900; data branch 950; formGroups branch 1000; attributes branch 1050; scripts branch 1100; and message box (“Msgbox”) branch 1150. Other storage branches may alternatively be used.

Exam branch 550, as seen in FIG. 12, stores, for example, the primary attributes, properties, and data that govern the test. Exam branch 550 can store information for various tests, as is denoted by the three, vertical ellipses. A specific test is identified by the data stored in name attribute storage 552. Again, the various tests may each be identified, for example, by a different name, as denoted by the solid border around name attribute storage 552 or other identification scheme. Attributes storage 554 stores, for example, version information 555, and title information 556 of the test as a stream of data. Title information 556 is optional, as is denoted by the broken border. Any optional, customized information regarding the test is stored in custom properties 558 as a property storage. Information relating to the forms of the test are optionally stored in forms property storage 560. A form is a fixed or substantially fixed order of testing events. Many different forms can be stored in forms storage 560, giving flexibility to test driver 110 in controlling progression of the test. FormGroups storage 562 optionally stores information relating to a collection of exam forms as a stream of data. Preferably, a single form from the formGroup is chosen to deliver to an examinee. The slection of the form from the group is performed by a selection plugin 160. Exam branch 550 preferably contains at least one forms storage 560 either independently or within formGroups storage 562. Other information relating to the test may be stored under exam branch 550. Other storage formats may optionally be used.

Forms branch 600, as seen in FIG. 13, stores, for example, the primary attributes, properties, and data that govern the progress of the test. Forms branch 600 can store information for various forms, as is denoted by the three, vertical ellipses. As described previously, a form is a fixed or substantially fixed order of testing events. A single form is identified by the data stored in name attribute storage 602. Other identification formats may optionally be used. Again, the various forms may each be identified by a different name, as denoted by the solid border around name attribute storage 602. Attribute storage 604 stores, for example, begin section information 605, end section information 606, event information 607, and optionally stores version information 608, title information 609, skip allowed information 610, restartable information 611, with information 612, height information 613, and bit depth information 614. All information stored in attribute storage 604 is stored as a stream of data or other data storage format. Begin section information 605 and end section information 606 indicates, for example, respectively which section of the test begins and ends the test.

Event information 607 indicates, for example, the order of events of the test for that form. Each event has a name and is prefixed with an event type and a colon. Other formats are optional. The event type includes “section”, “report”, and “results”. Version information 608 and title information 609 indicate the version and title of the form, respectively. Skip allowed information 610 indicates, for example, whether or not by default skipping of sections is allowed. Restartable information 611 indicates, for example, whether the form can be restarted. Any optional, customized information regarding the form is stored in custom storage 616 as a property set or other data storage format. Timer storage 628 stores, for example, information relating to how the form is to be timed as a storage element. Attributes storage 630 stores, for example, the names of Timer Plugin 158 to be used with the form. Plugin data storage 632 and plugin data storage 633 store any data necessary for timer plugin 158 as a storage element and a stream of data, respectively. Plugin data storage 632 and plug in data storage 633 are optional. Scoring storage 634 stores, for example, information relating to the scoring of the form. Attributes storage 636 stores, for example, the name of scoring plugin 164 to be used with the form. Plugin data 638 and plugin data 639 optionally store any data needed for scoring Plugin 164 as a storage element and a stream of data respectively.

Items Branch 650, as seen in FIG. 14, stores, for example, the primary attributes, properties, and data that govern the items, or test questions, to be delivered to the examinee during the test. Items branch 650 can store information for various items, as is denoted by the three, vertical ellipses. A single item is identified by the data stored in name attributes storage 652. Again, the various items may each be identified by a different name, as denoted by the solid border around name attributes storage 652. Attributes storage 654 stores, for example, weight information 654, scored information 655, and optionally stores, for example, skip allowed information 656, title information 657, start information 658, finish information 659, and condition information 660. Weight information 654 indicates, for example, a value used for judging and scoring the item. In one embodiment, by default an item is given a weight of one in accordance with one embodiment, but other values may be utilized. Scored information 655 indicates, for example, whether or not the item is scored as opposed to whether the item is being used as an example. The default of scored information 655 is true. Skip allowed information 656 indicates, for example, whether the examinee can skip the item without answering.

Start information 658 indicates, for example, script execution at the beginning of the item and finish information 659 indicates, for example, script execution at the end of the item. Condition information 660 indicates, for example, whether or not there is a condition on the item being delivered to the examinee. The information stored in attributes storage 654 is stored as a stream of data or other data storage format. Data storage 662 and data stream 664 store any information regarding the properties of the item. For example, data storage 662 or data stream 664 can store the correct answer of a multiple choice item. Data storage 662 and data stream 664 stored the information as a storage element and a stream of data respectively. Any optional, customized information regarding the item is stored in customs storage 666 as a stream of data or other data storage format. Category storage 668 stores, for example, information relating to each category to which the item belongs. The information stored in category storage 668 preferably and optionally is redundant, as category branch 700 stores, for example, all the items within the specific categories. The reason for the optional redundancy is so that test driver 110 can quickly look up the category of any item.

Category branch 700, as seen in FIG. 15, stores, for example, the primary attributes, properties, and data that govern the test categories. A test category provides a grouping mechanism, which is independent of delivery of the test, allowing for exotic reporting and scoring if necessary. Category branch 700 is optional as denoted by the broken border. Category branch 700 can store information for various categories, as is denoted by the three, vertical ellipses. A single category is identified by the data stored in name attributes storage 702. Again, the various categories may each be identified by a different name, as denoted by the solid border around name attributes storage 702. Attributes storage 704 stores, for example, complete information 705, duplicates information 706, contents information 707, and optionally stores, for example, description information 708. Complete information 705 indicates, for example, whether or not every item in the category must appear within the category or within its subcategories. Duplicates information 706 indicates, for example, whether the item can appear more than once within the category or within the subcategories. Contents information 707 determines what can exist within a category. Description information 708 is used within the category to contain a description of the category's contents. Category storage 710 stores, for example, information relating to any subcategories under the category identified in name attribute storage 702. Items storage 712 indicates, for example, any items that exist within the category. Sections storage 714 contains information indicating what any sections that exist within the category. Scoring storage 716 contains information relating to the scoring of the items within the category. Attributes storage 718 stores, for example, the name of the scoring plugin to be used with the item. Data storage 720 and data stream 722 contain the information needed to initialize scoring plugin 164. Data storage 720 and data stream 722 store the information as a storage element and a stream of data respectively.

Templates branch 750, as seen in FIG. 16, stores, for example, the primary attributes, properties, and data that govern the templates used in the test. Template branch 750 can store information for various main templates, as is denoted by the three, vertical ellipses. A single main template is identified by the data stored in name attributes storage 752. Again, the various templates may each be identified by a different name, as denoted by the solid border around name attributes storage 752. Attributes storage 754 stores, for example, split information 756, order information 757, and optionally stores, for example, size information 759. Split information 656 defines how a specific area within the template is to be split or separated, for example, either by rows or columns. Size information 759 indicates, for example, possible values for describing the size of the template, for example, pixels, percentages, or html syntax. Template storage 760 stores, for example, information relating to any sub-templates to be used under the templates specified by the information in name attributes storage 752. Sub-templates are identified by the information in name attributes storage 762. Many sub-templates 760 can exist as denoted by the three vertical ellipses.

Areas storage 764 indicates, for example, information relating to the areas used within the template denoted by the information in name attributes storage 752. Many areas may exist within a template as denoted by the three vertical ellipses. Each area is identified by the information stored in name attribute storage 766. Attribute storage 768 stores, for example, visible plugin name information 760, size information 770, and allow more information 771. Plugin name information 760 indicates, for example, the name of the visible plugin to be used with the area. Size information 770 indicates, for example, the size of the area, as for example a pixel value, a percentage value, or HTML syntax. Plugin data 772 and plugin data 774 store information relating to the visible plugin to be used in the area. The data stored in either plugin data storage 772 or plugin data stream 774 is executed by the visible plugin when the template is loaded. Plugin data storage 772 and plugin data stream 774 stores, for example, the information as either a storage element or a stream of data, respectively. Other information may optionally be stored.

Section branch 800, as seen in FIG. 17, stores, for example, the primary attributes, properties, and data that govern test sections. Test sections dictate the navigation and timing of groups of items as well as displays within the test. Sections branch 800 can store information for various sections, as is denoted by the three, vertical ellipses. A single section is identified by the data stored in name attribute storage 802. Again, the various sections may each be identified by a different name, as noted by the solid border around name attributes storage 802. Attributes storage 804 stores, for example, group information 805 and optionally stores, for example, title information 806, skip allowed information 807, start information 808, finish information 809, and condition information 810. Group information 805 indicates, for example, to which group of the test the section belongs. Skip allowed information 807 indicates, for example, whether or not the items within the section may be skipped. Start information 808 indicates, for example, script execution at the beginning of the section and finish information 809 indicates, for example, script execution at the end of the section. Condition information 810 indicates, for example, any conditions that exist regarding the section. Any optional, customized information regarding this section is stored in custom property storage 812 as a stream of data or other data storage format. Custom attributes will be stored as a property set. The “key” for each attribute will be a string.

Timer storage 814 stores, for example, information regarding the timing of the section. Attribute storage 816 stores, for example, information identifying timer plugin 158, which is to be used with a section. Plugin data storage 818 and plugin data storage 820 stores, for example, data needed for timer plugin 158. Plugin data storage 818 and plugin data storage 820 stores, for example, information as a storage element and a string of data or other acceptable format respectively. Navigation storage 822 stores, for example, information relating to the delivery of presentations and groups within the section. Attributes storage 824 stores, for example, information indicating which navigation plugin 162 is to be used with this section. Plugin data storage 826 and plugin data stream 828 store information needed for the navigation plugin 162. Plugin data storage 826 and plugin data stream 828 store the information as a storage element and a stream of data respectively. Groups branch 850, as seen in FIG. 18, stores, for example, the primary attributes, properties, and data that govern the groups within the test. A group determines the order of events within the test. Groups branch 850 can store information for various groups, as is denoted by the three, vertical ellipses. A single group is identified by the data store in name attributes storage 852. The various groups may each be identified by a different name, as noted by the solid border around name attributes storage 852. Attributes storage 854 stores, for example, type information 855, event information 856, title information 857, and reviewed name information 858. Type information 855 indicates, for example, whether the group is either a “group holder” (group of presentations), or a “section holder” (group of sub-sections). These are mutually exclusive.

Event information 856 indicates, for example, the order of events within the test. Review name information 858 indicates, for example, whether or not a presentation within the group is to be used as a review screen. Any optional, customized information regarding the group is stored in custom storage 860 as a stream of data or other data storage format. Events storage 862 stores, for example, event information as is described in further detail in FIG. 19. Scoring storage 864 stores, for example, information relating to the scoring of items within the group. Attributes storage 866 stores, for example, information indicating which scoring plugin 164 is to be used with the group. Selection storage 872 stores, for example, information relating to the selection of items within the group. Attributes storage 874 indicates, for example, which selection plugin 160 is to be used with the group.

FIGS. 19A, 19B, 19C, and 19D illustrate the events sub-branch of groups branch 850 in greater detail in accordance with one embodiment of the invention. In FIG. 19A, events sub-branch 862 can store information for various events. For example, events sub-branch 862 is storing information in events name sub-branch 880, event name sub-branch 890, and event name sub-branch 897. Attributes storage 881, in FIG. 19B, under events name storage 880 stores, for example, type information 882, template information 883, and optionally stores title information 884, counted information 885, start information 886, finish information 887, and condition information 888. Type information 882 indicates, for example, whether the event is an item or a display. Template information 883 indicates, for example, which template is being used with the event. Counted information 885 indicates, for example, whether a presentation should be included in the totals of presentations presented to the examinee in a section. Generally, presentations with items, or questions, are counted and introductory presentations are not counted. Start information 886, finish information 887, and condition information 888 indicates, for example, start, finish, and conditional scripts respectively. Any optional, customized information regarding the event is stored in custom storage 889. The “key” for each custom attribute will be a string. Referring again to FIG. 19A, event name storage 890 indicates, for example, a different event, which contains different attributes. Additionally, area information 891, in FIG. 19B, indicates, for example, which area is rendering the presentations content and item information 892 indicates, for example, the name of the associated item if the event is of the item type. Additionally, data storage 893, data stream 894, data storage 895, and data storage 896 contain information used in a nested presentation. The data off of a nested presentation are the contents of the item or the presentation. This data may be a stream, a storage, a link to a stream, a link to a storage, or other format. In FIG. 19C, event name 897 indicates, for example, another event, which includes a sub-event 898, in FIG. 19D.

Plugins branch 900, as seen in FIG. 20, stores, for example, the primary attributes, properties, and data that govern any plugins 150 used for the test. Plugins branch 900 can store information for various plugins, as is denoted by the three, vertical ellipses. A single plugin is identified by the data stored in name attribute storage 902. A CLSID is stamped with the name of the plugin 150. Attributes storage 904 stores, for example, information identifying the plugin 150 by a program ID. Data storage 906 stores, for example, the data, for example, as either a stream, set of data, or as a storage element if plugin 150, respectively.

Data branch 950, as indicated in FIG. 21, stores, for example, any global data needed for the test. Data stored optionally under data branch 950 may be stored as either a storage element or a stream of data as indicated by data storage 952 and data storage 954. Data stored under data branch 950 may be directly used by a plugin 150 or the data may be resources (.gif, .jpeg, .wab, .mpeg, etc.) used internally by a plugin 150.

FormGroups branch 1000, as seen in FIG. 22, stores, for example, the primary attributes properties and data that govern the formGroups of the test. FormGroups branch 1000 can store information for various formGroups, as is denoted by the three, vertical ellipses. A single formGroup is identified by the data stored in name attributes storage 1002. The various formGroups may each be identified by a different name, as denoted by the solid border around name attributes storage 1002. Attributes storage 1004 stores, for example, information indicating which forms are to be used within the formGroup. Selections storage 1006 stores, for example, information relating to the selection of items within the formGroup. Attributes storage 1008 indicates, for example, which selection plugin 160 is to be used with the formGroup. Plugin data storage 1010 and plugin data storage 1012 store any information needed for the selection plugin 160. Attributes storage branch 1050 stores, for example, attribute information that is global to exam resource file 120. This includes the last execution state of XXL compiler 140 [sMode], the major [iXXLMajorVersion] and the minor version [iXXLMinorVersion] of the XXL language.

Scripts branch 1100 stores, for example, information relating to scripts used within the test. Attributes storage 1102 stores, for example, type information that specifies which type of language the script is in. For example, VB script of J script. Scripts storage 1104 stores, for example, global scripts used within the test that may be referenced by the test driver. MsgBox branch 1150 stores, for example, information relating to the size and content of any message boxes that may be delivered to the examinee during the test. Message boxes may be triggered by plugins 150 during the exam.

D. POLESS Exam Instance File

FIGS. 26A, 26B, 26C, and 26D illustrate the POLESS layout of exam instance file 170 according to the present invention. Exam instance file 170 stores, for example, information regarding the current examinee's test. Exam instance file 170 is created when a test starts for an examinee. Exam instance file 170 is destroyed when the test successfully completes. If the examinee must restart her test due to some interruption, for example, a power failure, the state of the test is restored from Exam instance file 170. In a preferred embodiment, the layout of exam instance file 170 is in a hierarchical POLESS format. As seen in FIG. 26A, the top-level storage branches of exam instance file 170 from root 1200 are, for example: running branch 1202; contents branch 1310; and history branch 1320. Root 1200 relates to POLESS cStorageRoot class 406 (FIG. 26), which instantiates exam instance file 170.

Running branch 1202 stores, for example, the state information of all running objects in test driver 110 and plugins 150. Plugins 150 use one of IPersistInstanceStream interface 196 a, IPersistInstanceSet interface 196 b, or IPersistInstanceStore interface 196 c to store information to exam instance file 170 as a stream of data, a set of data, or a store of data, respectively. Any of plugins 150, except display plugin 152, results plugin 166, report plugin 168, and helm plugin 154, which do not contain examination state information, store examination state information to exam instance file 170. Test driver 110 determines the storage location in exam instance file 170 that stores, for example, a particular piece of examination state information.

Exam sub-branch 1204 contains examination state information relating to the exam. Contents storage 1206 stores, for example, exam status information 1207 and version information 1208. Exam status information 1207 indicates, for example, the status of the exam, for example, initializing or terminating. Template storage branch 1210 stores, for example, examination state information relating to templates running in the exam. Name attribute storage 1212 stores, for example, count information 1214 and observed ever information 1215. Observed ever information 1215 indicates, for example, whether or not the template's content has ever been fully seen by the examinee.

Form storage branch 1216 contains information relating to the forms used within the exam. Contents storage branch 1218 stores, for example, seconds information 1219, date start information 1220, date finish information 1221, current section information 1222, and version information 1223. Current section information 1222 indicates, for example, the current section being delivered to the examinee in the form. Version information 1223 indicates, for example, the identification of the form.

Sections chosen storage branch 1224, as illustrated in FIG. 26B, stores, for example, information relating to sections in the form being delivered to the examinee. Contents storage 1226 stores, for example, the names of the sections that have been or will be delivered to the examinee. Name attribute storage 1228 indicates, for example, the name of a particular section. Contents storage 1230 stores, for example, current child information 1231, seconds information 1232, date start information 1233, and date finish information 1234. Navigation storage 1236 and navigation storage 1237 store the state information of navigation plugin 162. Navigation storage 1236 stores, for example, the examination state information from navigation plugin 162 if navigation plugin 162 implements the IPersistInterfaceSet 196 b or IPersistInterfaceStore 196 c. Navigation storage 1237 stores, for example, the information from navigation plugin 162 if navigation plugin 162 implements IPersistInterfaceStream 196 a. Timers storage 1238 and timers storage 1239 store information from timer plugin 158. Timer storage 1238 is used if timer plugin 158 implements IPersistInterfaceSet 196 b or IPersistInterfaceStore 196 c. Timers storage 1239 is used if timer plugin 158 uses IPersistInterfaceStream 196 a.

Items chosen sub-branch storage 1240 stores, for example, information relating to items that have been or will be delivered to the examinee. Contents storage branch 1242 stores, for example, the names and order of all the items that have been or will be delivered to the examinee. Name attributes storage 1244 indicates, for example, the identification of a particular item. Contents storage branch 1246 stores, for example, presented information 1244, complete information 1248, skipped information 1249, seconds information 1250, dehydrated information 1251, and observed ever information 1252. Presented information 1247 indicates, for example, whether the item has ever been delivered to the examinee. Completed information 1248 indicates, for example, whether or not the item has been completed. Skipped information 1249 indicates, for example, whether the item has been skipped. Item plugin storage 1254 and item plugin storage 1255 stores, for example, examination state information from item plugin 156. Item plugin storage 1254 is used if item plugin 156 uses IPersistInterfaceSet 196 b or IPersistInterfaceStore 196 c. Item plugin storage 1255 is used if item plugin 156 uses iPersist interface 196A.

In FIG. 26C, item light storage 1256 exists only if the item was dehydrated (to save memory or when a section ends). The dehydrated item stores the data but actions on the data are no longer available until the item is rehydrated. Item light storage 1256 stores, for example, score candidate information 1257. Score minimum information 1258, score nominal information 1259, score maximum information 1260, complete information 1261, skipped information 1262, correct answer display 1263, response results 1264, and correct answer results 1266. Timers storage 1268 and timers storage 1269 store information from timer plugin 158. Timer storage 1268, as seen in FIG. 26B, is used if timer plugin 158 implements IPersistInterfaceSet 196 b or IPersistInterfaceStore 196 c. Timers storage 1269 is used if timer plugin 158 uses IPersistInterfaceStream 196 a. Score storage 1270 and Score storage 1271 store information from timer plugin 158. Timer storage 1270 is used if timer plugin 158 implements IPersistInterfaceSet 196 b or IPersistInterfaceStore 196 c. Score storage 1271 is used if timer plugin 158 uses IPersistInterfaceStream 196 a.

In FIG. 26C, groups chosen sub-branch storage 1272 indicates; for example, which groups have been or will be delivered to the examinee. Contents storage 1274 stores, for example, the names of the groups. Name attributes storage 1276 indicates, for example, the name of a particular group. Contents storage 1278 stores, for example, names of groups and the order of groups. Scoring storage 1280 and scoring storage 1281 store examination state information from score plugin 164. Scoring storage 1280 is used if score plugin 164 implements IPersistInterfaceSet 196 b or IPersistInterfaceStore 196 c. Scoring storage information 1281 is used if score plugin 164 implements IPersistInterfaceStream 196 a. Selection storage 1282 and selection storage 1283 store information from selection plugin 160. Selection storage 1282 is used if selection plugin 160 implements IPersistInterfaceSet 196 b or IPersistInterfaceStore 196 c. Selection storage 1283 is used if selection plugin 160 implements IPersistInterfaceStream 196 a. Delivered storage 1284, in FIG. 26D, stores, for example, an ordered list of groups chosen for delivery. Delivered storage 1285 stores an ordered list of the sub-classes of the form, for example: sections, reports and results.

Presentations chosen storage sub-branch 1286 indicates, for example, any presentations that have been or will be delivered to the examinee. Contents storage 1288 stores, for example, the names of the presentations. Names storage sub-branch 1290 stores, for example, the name of the presentation. Names storage 1290 also stores, for example, comment-information 1291, marked information 1292, count information 1293, name information 1294, observed ever information 1295, name information 1296, and observed ever information 1297. Name information 1294 and observed information 1295 relate to the name of the first presentation area stored under presentations chosen sub-branch 1286 and whether or not the presentation has ever been observed, and name information 1296 indicates, for example, the last presentation area that was delivered to the examinee and whether or not the presentation was ever observed. Contents storage 1298 stores, for example, information leading to events. Contents storage 1298 stores ready information 1299 ever checked information 1300, ever started information 1301, and ever finished information 1302. Ready information 1299 indicates, for example, whether the event is ready to be delivered to the examinee. Ever checked information 1300 indicates, for example, whether an event's conditional delivery script ever been checked. Preferably, the conditional delivery script is only checked once. Ever started information 1301 indicates, for example, whether the event was ever started by the examinee. Ever finished information 1302 indicates, for example, whether the event was completed by the examinee.

Referring again to FIG. 26A, contents branch 1310 stores, for example, a property set containing information to identify the examination instance and the examination start count 1312. The identifying information used is the examinee appointment identification 1311, the name 1313 of exam resource file 120, and the name 1314 of the specified form or group.

History branch 1320 is a single stream of chronological text messages that logs the history of the test. These text messages are used by staff at system headquarters to diagnose problems that occurred in the field. Each text message is prefixed with the date, time, and a level of severity, for example: information, warning, or error. Test driver 110 will filter the text messages to a level of diagnostics desired for test driver 110, such as determining errors in test driver 110 or detail history tracking, including general information.

V. Expansion of Test Driver Using Plugins

FIG. 27 illustrates the process for customizing test based on specific requirement from the client using plugins 150, denoted generally by reference numeral 1400. First, the client presents the new requirements, for example, a new item type, to the test developer, step 1402. The test developer then writes and XML schema to define the XXL test specification, step 1404. The schema is subsequently used to validate the XXL test specification. An example of the XXL schema is as follows:

  <!--   [linear_navigate-schema.xml]  _(—  )-->   <!-- ===================================================== ========= -->   <!--   -->   <!-- <linearNavigate>                           -->   <!--   -->   <!-- ATTRIBUTE      REQ? DESCRIPTION                       -->   <!-- initialReview    no    [true] (false) Whether a candidate may    -->   <!--   review items from the very beginning of a  -->   <!--   section.     -->   <!-- markAllowed        no    [true] (false) Whether a candidate may   -->   <!--                    mark items during the exam for_review    -->   <!--   purposes.   -->   <!-- incompleteEndAllowedno    [true] (false)_Whether a candidate may    -->   <!--                 end a   section that contains incomplete    -->   <!--   items.     -->   <!-- endSectionPrompt    no    The message to   disply when ending a    -->   <!--   section.     -->   <!-- endIncompleteSectionPrompt                           -->   <!--                no    The message to display when ending a    -->   <!--   section with incomplete items.        -->   <!-- quitExamPrompt     no     The message to disply when quiting an    -->   <!--                    exam.   -->   <!-- comment            no    [false] (true)  If the candidate can    -->   <!--                    make comments during this section.      -->   <!-- readOnly            no    [false] (true) If the items are set to    -->   <!--                    be read-only.                    -->   <!-- nextOrMore      no    [true] (false) Whether to show “Next”   -->   <!--   button with “More” button              -->   <!--   -->   <!-- SUB-ELEMENTS                           -->   <!-- none   -->   <!--   -->   <!-- NOTES   -->   <!-- -   Non-adaptive navigation plug-in.   -->   <!-- -   Allows for simple “movement” between items and sections -->   <!-- -   For “markAllowed” to have an effect a_helm which supports marking  -->   <!--    of items must be used in the exam too.                 -->   <!-- -   The button labels will appear exactly_as entered including      -->   <!--   capitalization.                       -->   <!-- -   It is a common case to set comment=“true” and readOnly=“true” and -->   <!--   re-deliver a section for the sole purpose of commenting.         -->   <!--   -->   <!-- ====================================================== ========= -->   <ElementType name=“linearNavigate” order=“many” content=“empty” model=“closed”>     <AttributeType name=“initialReview” dt:type=“enumeration” dt:values=“true false” default=“true” required=“no”/>     <AttributeType name=“markAllowed” dt:type=“enumeration” dt:values=“true false” default=“true” required=“no”/>     <AttributeType name=“incompleteEndAllowed” dt:type=“enumeration” dt:values=“true false” default=“true” required=“no”/>     <AttributeType name=“endSectionPrompt” dt:type=“string” required=“no” default=“This will end your section. Do you wish to end?”/>     <AttributeType name=“endIncompleteSectionPrompt” dt:type=“string” required=“no” default=“You have not fully answered all items. If you end incomplete items will be marked as incorrect. Do you wish to end?”/>     <AttributeType name=“quitExamPrompt” dt:type=“string” required=“no” default=“You are about to exit the exam. Do you wish to exit?”/>     <AttributeType name=“comment” dt:type=“enumeration” dt:values=“true false” default=“false” required=“no”/>     <AttributeType name=“readOnly” dt:type=“enumeration” dt:values=“true false” default=“false” required=“no”/>     <AttributeType name=“nextOrMore” dt:type=“enumeration” dt:values=“true false” default=“true” required=“no”/>     <attribute type=“initialReview”/>     <attribute type=“markAllowed”/>     <attribute type=“incompleteEndAllowed”/>     <attribute type=“endSectionPrompt”/>     <attribute type=“quitExamPrompt”/>     <attribute type=“endIncompleteSectionPrompt”/>     <attribute type=“comment”/>     <attribute type=“readOnly”/>     <attribute type=“nextOrMore”/>   </ElementType> The above sample schema is defining the attributes and elements associated with the top-level XXL element “linearNavigate.” A more detail description of the XXL schema is given in the co-pending application filed on the same date, entitled “EXTENSIBLE EXAM LANGUAGE (XXL) PROTOCOL FOR COMPUTER BASED TESTING,” incorporated herein by reference.

The test developer next writes the appropriate plugin 150, in this example, item plugin 156. The test developer also implements the IPlugin interface 167 and IPlugin interface and Iltem interfaces 169. Additionally, the test developer implements IPersistResource interface 192 (FIG. 3) to enable persistence of compiled test information from item plugin 156 to exam resource file 120. The test developer can optionally implement IPersistInstance interface 196 (FIG. 3), step 1408, to enable persistence of examination state information from item plugin 156 to exam instance file 170. After the appropriate interfaces have been implemented, item plugin 156 is valid and operating. Finally, after the test is delivered to the examinee, the result processor accumulates results from the examinee, 1410. The results processor must be able to understand the new item type to correctly process the results. Customization process 1400 only required the test developer to write one piece of software, item plugin 156, to accommodate the client's customizations rather than multiple pieces of software.

A. Plugin Life Cycle

FIG. 28 illustrates the life cycle of plugin 150 from test production to test delivery, denoted generally by reference numeral 1420. Dashed vertical line 1422 divides the plugin life cycle 1420 into a test production cycle, to the left of dashed vertical line 1422, and a test delivery cycle, to the right of dashed vertical line 1422. The test production cycle occurs only occasionally when new plugins 150 are developed to satisfy the requirements of a client. The test delivery cycle occurs whenever the test is delivered to the examinee, for example, daily.

Exam source files 130, of which data files 132 and XXL files 134 are shown, contain every aspect of the test as written by the test publisher. In step I, XXL compiler 140 reads from XXL files 134 and interprets instructions that call for the use of a plugin 150. Plugin 150 is identified in the XXL test definition language by both a name and a program identification (“prog ID”). When XXL compiler receives the prog ID from XXL files 134, XXL compiler knows that a plugin 150 is required to complete the compilation of exam source files 130. An example of plugin 150 calls in XXL is as follows:

<?xml version=“1.0” ?> <xxl version=“1.16” xmlns=“x-schema:c:\UTDSDK\xxl-master- schema.xml”>  <!-- ====================================================== ======  -->  <!--   -->  <!--   This contains all of the plugins used for this exam.         -->  <!--   -->  <!-- ====================================================== ======  -->  <!-- TIMERS -->  <plugin name=“clockTime” progid=“UTDP.StandardTimer”/>  <!-- SCORING -->  <plugin name=“testScore” progid=“UTDP.ScoreTable”/>  <!-- RESULTS -->  <plugin name=“testResults” progid=“slsOutputPlugin.cOutputResults”/>  <!-- NAVIGATIONS -->  <plugin name=“refNav” progid=“REF.cNavigation”/>  <plugin name=“linearNav” progid=“UTDP.cLinearNavigate”/>  <!-- SELECTIONS -->  <plugin name=“sequential” progid=“UTDP.SequentialExhaustive”/>  <!-- DISPLAYS -->  <plugin name=“label” progid=“REF.udLabel”/>  <!-- ITEMS -->  <plugin name=“hotArea” progid=“hotArea.hotAreaItem”/>  <plugin name=“multi” progid=“UTDP.MultiChoiceItem”/>  <!-- HELMS -->  <plugin name=“backForward” progid=“REF.udBackForward”/> </xxl>

The ten plugins defined in the previous example represent eight different types of plugins 150. Not all of the possible types of plugins 150 are required to build any one test. Also, more than one plugin 150 is implemented for a specific type. In the above example, two navigation plugins 162 and two item plugins 156 are defined. XXL compiler 140 reads information from exam source files 130 using IStream interface 340, iNode interface 1424, and IStreamVB interface 348. XXL compiler 140 instantiates the requested plugin 150 using, for example, the call CoCreateInsance. CoCreateInsance( ) creates a single, uninitialized object of the class associated with a specified CLSID, using a prog ID that has been converted into the CLSID.

If the data referring to plugin 150 has been customized by the test developer, XXL compiler 140 may not recognize the new data. Therefore, XXL compiler 140 passes the data directly to plugin 150 and plugin 150 loads the data into a private memory (not shown). In one embodiment, the private memory is internal to plugin 150, and in another embodiment, the private memory is external to plugin 150. Plugin 150 can then validate the data using the XXL schema. If the data is invalid, plugin 150 reports the error. In an alternative embodiment, plugin 150 can validate the data using an XML document type definition (“DTD”). A DTD is a formal description in XML Declaration Syntax of a particular type of document. Similar to a schema, a DTD sets out what names are to be used to the different types of elements, where they may occur, and how they all fit together. However, the XXL schema is preferred for validation since schemas are easier to read than a DTD and are very flexible.

If plugin 150 declares that the data is valid, XXL compiler 140 prepares a POLESS storage object 300 in exam resource file 120 to which plugin 150 saves the data at a command from XXL compiler 140, in step II. As described previously, XXL compiler 140 determines where the data from plugin 150 is to be saved in exam resource file 120 and creates the appropriate storage location. The name, CLSID, and data associated with plugin 150 is stored in plugins branch 900 in exam resource file 120 (FIG. 20). Plugin 150 implements IPersistResource interface 192 to store the data to exam resource file 120. Data storage 906 stores, for example, the data as either a set of data or as a storage element if plugin 150 implements either IPersistResourceSet interface 192 b or IPersistResourceStore interface 192c, respectively. Data storage 908 stores, for example, the data as a stream of data if plugin 150 implements IPersistResourceStream interface 192 a. Plugin 150 can choose the format used to store the data into exam resource file 120. Steps I and II are repeated until exam source files 130 are completely compiled and exam resource file 120 is completely populated with the compiled test information.

The compile sequence of a plugin 150, as shown in steps I and II in FIG. 28, are illustrated in greater detail in FIG. 29. Plugin compile sequence 1430 begins as XXL compiler 140 asks plugin 150 to validate the information from exam source files 130 that pertain to plugin 150 using IPlugin::ValidateSource( ) call 1432, in step I. Plugin 150 validates whether or not the data received from exam source files 140 is correctly formatted based on the XXL schema. If the data is not valid, plugin throws, for example, a structured COM error. Plugin 150 does not validate that all required source elements are present, but rather, that what is present is correctly formatted.

Step II contains two steps, indicated as step IIa and IIb. In step IIa, XXL compiler 140 creates the appropriate storage element in exam resource file 120 using POLESS object 300. The storage element type is determined based on the type of. IPersistResource interface 192 that plugin 150 implements, for example: IPersistResourceStream interface 192 a; IPersistResourceSet interface 192 b; or IPersistResourceStore interface 192 c. XXL compiler 140 then calls IPersistResource*::Save( ) call 1434 for the appropriate IPersistResource interface. Plugin 150 saves the compiled information from exam source files 130 to exam resource file 120 through the POLESS object 300 passed by XXL compiler 140. In step IIb, XXL compiler 140 instructs plugin 150 to unload, or flush, its content using Unload( ) call 1436. As stated previously, steps I, IIa, and IIb are repeated until all of exam source files 130 is compiled.

Step VI, which is shown as steps VIa and VIb, concerns amalgamation of exam resource file 120. Amalgamation enables data for a specific plugin to exist virtually as one storage location even if the data appears at different locations within the storage hierarchy. Amalgamation can be performed on exam resource file 120 if plugin 120 has implemented either IPersistResourceSet interface 192 b or IPersistResourceStore interface 192 c which storing data to exam resource file 120. In step VIa, XXL compiler 140 amalgamates one to three storage elements in exam resource file 120 and passes the amalgamated POLESS object to plugin 150 using IPersistResource*::ValidateResource( ) call 1438. Plugin 150 determines whether or not the amalgamated POLESS object creates a complete and valid set. Plugin 150 throws, for example, a structured COM error if the amalgamated POLESS object does not create a complete and valid set. In step VIb, XXL compiler 140 instructs plugin 150 to unload, or flush, its content using Unload( ) call 1440. Steps VIa and VIb are interspersed among steps I, IIa, and IIb cycles and can also occur multiple times during the compilation of exam source files 130. Amalgamation will be explained below in greater detail.

Referring again to FIG. 28, during the test delivery cycle, test driver 110 reads the test specifications stored in exam resource file 120 through POLESS objects 300. Test driver 110 reads information from exam resource file 120 through POLESS objects 300 in order to retrieve the encrypted, compressed, and structured elements within exam resource file 120. When the XXL test definition language calls a plugin 150 by a prog ID, as described previously, test driver 110 instantiates the plugin 150 that was called, in step III. Test driver 110 provides the POLESS object 300 from exam resource file 120 and plugin 150 initializes itself from the POLESS object 300, for example, data storage 906 or data storage 908 stored under name attribute storage 902, using the appropriate IPersistResource interface 192. The information loaded into plugin 150 is the same information as was stored into exam resource file 120 by plugin 150 during the test production cycle (step II). Since,plugin 150 chose the storage format used to store the information into exam resource file 150, plugin 150 can always read the information from exam resource file 150, giving plugin 150 complete flexibility. Test driver 110 need not be able to read the information that is used by plugin 150. Therefore, any customizations to the test facilitated by plugin 150 does not require any changes to test driver 110. The test then progresses with plugin 150 enhancing the functionality of test driver 110 based on the new requirements from the client.

Periodically, based on a request either from test driver 110 or from plugin 150, the state of all running objects will save to exam instance file 170, which is a unique file for each examinee, indicating the progress and the status of the test for that examinee. Test driver 110 asks plugin 150 if plugin 150 is “dirty,” meaning that plugin 150 is storing has some updated examination state information. For example, when the examinee selects distractor A on a multi-choice item, item plugin 156, in this case, becomes dirty. If plugin 150 is dirty, test driver 110 provides plugin 150 a POLESS object 300 in exam instance file 170 and plugin saves the examination state information to exam instance file 170 using IPersistInstance interface 196, in step IV. For example, item plugin 156 saves the examinee's answer to item plugin storage 1254 or to item plugin storage 1255 (FIG. 26). Item storage 1254 stores, for example, the data as either a set of data or as a storage element if item plugin 156 implements either IPersistInstanceSet interface 196 b or IPersistInstanceStore interface 196 c, respectively. Item storage 1255 stores, for example, the data as a stream of data if item plugin 156 implements IPersistInstanceStream interface 196 a.

Step V occurs if the test is interrupted, for example, because of a power failure, and the test needs to restart. When test driver 110 is required to return to a particular operation state, test driver 110 reads the examination state information from exam instance file 170. Plugin 150 is provided the storage object containing the state of plugin 150 as saved in step IV using IPersistInstance interface 196. Using the previous example, item plugin 156 retrieves its state information from item plugin storage 1254 or for item plugin storage 1255. Plugin 150 is able to become operational from the retrieved state information, enabling a restart of the test from the point at which the test was interrupted.

The delivery sequence of a plugin 150, as shown in steps II, IV, and V in FIG. 28, are illustrated in greater detail in FIGS. 30A, 30B, 30C, and 30D. As seen in FIG. 30A, delivery sequence 1520 particularly relates to visible plugins 150, e.g., display plugin 152, helm plugin 154, and item plugin 156. Step III contains sub-steps labeled IIIa-IIIb. Plugin delivery sequence 1520 begins, in step IIIa, when the current delivering presentation requests its template to activate with cTemplate::Activate( ) call 1524. Activate( ) call 1524 is activated when the examinee navigates on the test using a helm navigation control activated by helm plugin 154. IContainerNotifyHelm interface 206 allows helm plugin 154 to request navigation from test driver 110. IContainerNotifyHelm interface 206 sends Activate( ) call 1524 to cTemplate class 236 in test driver 110 (see FIG. 8).

In step IIIb, cTemplate class 236 in test driver 110 uses IPlugin::Load( ) call 1526 to set the core object references from test driver 110 into the plugin 150 being delivered. The core object references include IContainerNotify interface 200, the cExam class (not shown), and the IAppointment interface 176, which passes information regarding the examinee and appointment to plugin 150.

Step V, which is interspersed with step III, occurs only if the test is interrupted and plugin 150 loses state. cTemplate class 236 in test driver 110 uses IPersistInstance*::Reload( ) call 1528 to call on the reload method of exam instance file 170. Exam instance file 170 reloads plugin 150, through IPersistInstance interface 192, for example, IPersistInstanceSet 192 b, with the state saved to the appropriate storage location in exam resource file 170 (see FIG. 26).

Step IIIc is performed for both initial delivery of plugin 150 and during restart of the test, in conjunction with step V. cTemplate class 236 in test driver 110 uses IPersistResource*::Load( ) call 1530 to call on the load method of exam resource file 120. Exam resource file 120 loads plugin 150, through IPersistResource interface 192, for example IPersistResourceSet interface 192 b, with the test specification and content from the appropriate storage location in exam resource file 120. Plugin 150 is loaded with test specification and content from exam resource file 120 when being initially delivered to the examinee. Plugin 150 is also loaded with test specification and content from exam resource file 120 and with examination state information from exam instance file 170, as described above, when the test has been interrupted and plugin 150 must recover state.

After plugin 150 is properly loaded, cTemplate class 236 in test driver 110 uses, I*::PresentationStarting( ) call 1532 to inform visible plugin 150 that the presentation is starting, in step IIId. I*::PresentationStarting( ) call 1532 is made to any visible plugin 150 being used in the presentation on the appropriate interface, for example: IDisplay interface 169 a, IItem interface 169 c, or IHelm interface 169 b. For example, an IItem::PresentationStarting( ) call is used for item plugin 156. cTemplate class 236 then instruct visible plugins 150 to display using IOleObject::DoVerb(Show, . . . ) command 1534, step IIIe. IOleObject interface 1522 is the Active Document interface used to implement the Active Document presentation. (See FIG. 3-1). IOleObject interface 1522 is the combination of the Active Document interfaces described in conjunction with FIG. 7. After instructing visible plugins 150 to display, test driver 110 awaits notification from each visible plugin 150 that the specific visible plugin 150 has successfully shown. Visible plugins 150 call back to test driver 110 using IContainerNotify::Activated( ) call 1536, step IIIf (continued in FIG. 30B). Now, the presentation is started and active such that the examinee can interact with the presentation.

The deactivation of the presentation begins with a request from the helm for navigation. For example, if the examinee has finished a question and wishes to move on to the next question on the next presentation, the examinee can choose the “NEXT” button on the helm. The navigation request is sent from IHelm interface 169 b, which receives the request from the examinee, to test driver 110 using IContainerNotifyHelm interface 206. As seen in FIG. 30D, the request is made using IContainerNotifyHelm::RequestMove( ) call 1538, step IIIg. Test driver 110 then asks each item plugin 156 being used in the presentation template if the examinee is allowed to leave the current presentation and to proceed to the next presentation. The query is made using IItem::bProceed( ) call 1540, step IIIh. If all item plugins 156 respond in the affirmative, test driver 150 passes the navigation request to navigation plugin 162, which is an invisible plugin 150. Test driver 110 passes the request using INavigate::RequestMove( ) call 1542, step IIIi. Navigation plugin 162 determines the resultant location of the requested navigation. In FIG. 30, for example, navigation plugin 162 determines the section of the test to which the examinee will proceed using ISection::ChildNext( ) call 1544, step IIIj.

The active presentation then instructs the template to deactivate using cTemplate::Deactivate( ) call 1546, step IIIk (continued in FIG. 30C). Referring back to FIG. 30D, cTemplate class 236 in test driver 110 requests that visible plugins 150 hide from the Active Document using IOleObject::DoVerb(Hide, . . . ) call 1548, step III. cTemplate class 236 in test driver 110 informs visible plugins 150 that the current presentation is ending using I*::PresentationEnding( ) call 1550, step IIIm. For example, cTemplate informs helm plugin 154 that the current presentation is ending using the IHelm::PresentationEnding( ) call.

Step IV, which contains sub-steps IVa-c, is the process to save plugin state data to exam instance file 170. Test driver 110 requests the “dirty” state of plugin 150 to determine whether plugin 150 is storing any state information that would be necessary if the test were to be interrupted. Test driver 110 uses IPersistInstance*::IsDirty( ) call 1552 to make the request, step IVa. For example, test driver 110 uses IPersistInstanceSet::IsDirty call 1552 if the state data is a property set. If plugin 150 is storing state data that is not already stored in exam instance file 170, IPersistInstance*::IsDirty( ) call 1552 returns true. If plugin 150 is “dirty”, test driver 110 instructs plugin 150 to save the state data to exam instance file 170 in the POLESS object provided (FIG. 26) using IPersistInstance*::Save( ) call 1554, step IVb. Finally, test driver 110 instructs plugins 150 to unload all objects using IPlugin::Unload( ) call 1556, step IVc.

B. Amalgamation of Plugins in Exam Resource File

The test publisher defines common plugin 150 test specification and common plugin 150 test content in early XXL elements in XXL files 134. These previous elements can be referenced by later XXL elements in XXL files 134. When XXL files 134 are initially compiled into exam resource file 120, the relational hierarchy of the XXL elements is maintained. However, through amalgamation, these separate elements are brought together, or amalgamated, into one, virtual storage location in exam resource file 120. The storage location is virtual because the storage location does not physically exist but acts identically to a physical storage for read-only purposes. If the later element defines nothing more then plugin 150 will receive just the common specification and content.

Optionally, the later elements can define omitted non-common plugin 150 specification and contents. Further, the later elements can override previously defined common plugin 150 specification and contents with exception plugin 150 specification and contents. This process of new definition and overriding of specification and contents by later XXL elements is not limited to two stages. Multiple later stages are allowed.

When test driver 110 uses plugin 150 to deliver the test, plugin 150 uses the specification and contents to determine how and what to deliver. The specification and contents used by plugin 150 is the amalgamation of all relevant XXL elements in exam resource file 120. The amalgamation is invisible to plugin 150 and requires no special effort for plugin 150 during delivery. The amalgamation occurs at delivery time and therefore common specification and content appear only once in the compiled exam resource file 120. Thus, the size of the exam resource file 120 is reduced.

1) Invisible Plugins

The XXL language allows invisible plugins 150 (e.g., timer plugin 158, selection plugin 160, navigation plugin 162, scoring plugin 164, results plugin 166, and report plugin 168) two locations to define test specification and content. These two locations are the element storing identification and initialization data for plugin 150 stored under plugins branch 900 in exam resource file 120 and the storage location containing the information that defines the actual usage of plugin 150 on a unit of the test. Invisible plugins 150 are defined for usage in forms branch 600, sections branch 800, category branch 700, and groups branch 850 in exam resource file 120. Test driver 110 amalgamates these two levels during delivery of the test.

Data storage 906 under plugins branch 900 in exam resource file 120 stores, for example, plugin 150 specification and content. Data storage 906 is the first data location for the amalgamation. Data storage 908, which stores, for example, a stream of data, is not involved in amalgamation since amalgamation can only be performed on a set of data or a storage element. Below is a sample of plugin 150 elements:

<!-- Navigation --> <plugin name=“controlledNav”   progid=“AICPAPlugins.controlledNav” /> <plugin name=“linearStandard” progid=“UTDP.cLinearNavigate”>  <data>   <linearNavigate    initialReview=“true”    endIncompleteSectionPrompt=“You have not answered all the questions”    quitExamPrompt=“Click ‘Yes’ to quit. Otherwise, click ‘No’ to continue.”    endSectionPrompt=“Are you ready?”/>  </data> </plugin> <plugin name=“linearIntro” progid=“UTDP.cLinearNavigate”>  <data>   <linearNavigate    initialReview=“true”    endIncompleteSectionPrompt=“Do you wish to begin the exam?”    endSectionPrompt=“Do you wish to begin the exam?” />  </data> </plugin>

The XXL source above defines three navigation plugins 162 for use in the test. The first is named “controlledNav” and does not have any test specification or test content defined that is common to all “controlledNav” navigation plugins 162 for this particular test. The second is named “linearStandard” and does have test specification and test content defined that is common to all “linearStandard” navigation plugins 162 in the test. The third is named “linearIntro” and also has test specification and test content defined that is common to all “linearIntro” navigation plugins 162 in the test. Notice that both “linearStandard” and “linearIntro” utilize the same navigation plugin 162 code component with the prog ID of UTDP.cLinearNavigate. The elements of both “linearStandard” and “linearIntro” contain many of the same attributes, but only the “linearStandard” has the quitExamPrompt defined for it. Also, some of the common attributes have the same values and some have different values, for example, “endSectionPrompt”.

Data storage 826 under navigation storage 822 and data storage 818 under timer storage 814 in sections branch 800 in exam resource file 120 also store plugin 150 specification and content. These are the second data locations for the amalgamation. Below is a sample of navigation and timer elements under the section element:

<section name=“testlet001”>  <navigation plugin=“linearIntro” />   <timer plugin=“timerStandard”>    <data>     <stanardTimer timed=“false” contributing=“true” />    </data>   </timer>  <groupRef name=“gtestlet001” /> </section> <section name=“testlet002”>  <navigation plugin=“linearIntro”>   <data>    <linearNavigate     initialReview=“true”     quitExamPrompt=“Click ‘Yes’ to quit the test then, raise your hand.”   </data>  </navigation>  <timer plugin=“timerStandard” />  <groupRef name=“gtestlet002” /> </section>

The XXL source above defines two navigation plugins 162 and two timer plugins 158 used to deliver the test. The first navigation plugin 162 instance, “linearIntro”, which was defined in the previous example, is located in the section named “testlet001”. Since no additional data is defined for “linearIntro” under “testlet001”, the section definition language does not override or extend the original common specification and content for “linearIntro”.

The second navigation plugin 162 instance, also using “linearIntro”, is located in the section named “testlet002”. Since “testlet002” does define data for “linearIntro”, the new specification and content defined in the section definition language will be amalgamated with the common specification and content originally defined for “linearIntro”. (See previous example.) The new specification and content does override the original value for “initialReview” and extends the original common specification by defining a value for “quitExamPrompt”. Note, however, that although the initial and later values for “initialReview” are both “true”, the later value does override the initial value. If the later value were different than the original value, the value for “initialReview” would change.

FIG. 31 is a flow chart illustrating the overall process for amalgamation of invisible plugins, denoted generally by reference numeral 1549. A first segment of the test specification and content, stored under plugins branch 900 is validated by the appropriate invisible plugin 150, step 1551. A second segment of the test specification and content, stored in the storage location containing the information that defines the actual usage of the invisible plugin 150, is then validated by the same invisible plugin 150, step 1553. The first segment and the second segment are then amalgamated, step 1555. The amalgamated segment is validated by the invisible plugin 150 to determine whether the amalgamated segment forms a complete and valid set, step 1557. During delivery of the test, the first segment and the second segment are reamalgamated, step 1558, and the reamalgamated segment is delivered to the examinee, step 1559.

2) Visible Plugins

The XXL language allows three locations for visible plugins 150 (e.g., display plugin 152, helm plugin 154, and item plugin 156) to define test specification and content. These first two locations are the element storing identification and initialization data for plugin 150 stored under plugins branch 900 in exam resource file 120 and data storage 772 under area storage 764 in templates branch 750 of exam resource file 120. The third location is the events element 880, which is stored under groups branch 850, in the case of display plugins 152 or helm plugins 156. Alternatively, the third location is or data storage 662 under items branch 650, in the case of item plugins 156. Test driver 110 amalgamates these three locations during delivery by the test.

Data storage 772 under area storage 764 in templates branch 750 stores, for example, visible plugin 150 specification and content for use in a particular template. Data storage 772 is the second data location for the amalgamation for visible plugins 150. Below is a sample of area elements in a template element (note: “helmTitlebar” display plugin 152, “helmNextPrevious” helm plugin 154, and “itemMultiChoice” item plugin 156 are previously defined in XXL that is not shown):

<template name=“multiItem_Template” split=“rows”>  <area name=“titlebar” size=“40” plugin=“helmTitlebar”>   <data>    <titlebarHelm done=“false” calc=“false” help=“false” />   </data>  </area>  <area name=“item” plugin=“itemMultiChoice” size=“*” />  <area name=“helm” size=“40” plugin=“helmNextPrevious”>   <data>    <nextPrevious bgcolor=“#D4D0C8”>     <button action=“next” img=“../images/continue.bmp” />    </nextPrevious>   </data>  </area> </template>

The XXL source above defines one template named “multiItemTemplate”. This template contains three areas, named “titlebar”, “item”, and “helm”, and each area references one visible plugin 150 utilized in that area. For example, the area named “titlebar” utilizes “helmTitlebar” display plugin 152. The first and the third area define data in data storage 772 for display plugin 152, “helmTitlebar”, and helm plugin 156, “helmNextPrevious”, respectively, to be amalgamated with the specification and content stored in data storage 906 under plugins branch 900 for “helmTitlebar” and “helmNextPrevious”. The second area accepts the common item plugin 156 level specification and content for “itemMultiChoice” without further refinement.

Data storage 662 under items branch 650 or events element 880 in XXL under groups branch 850 contain plugin 150 specification and content for item plugins 150 or display plugins 152 and helm plugins 156, respectively. These are the final data locations for the amalgamation of visible plugins 150. Below is a sample of item elements:

<item name=″101A″ template=″multiItem_Template″ area=”item”>  <data>   <multiChoice    correctAnswer=″A″    maxResponses=″1″    minResponses=″1″    autoPrompt=″false″    URI=″..\itembank/itembank.htm#101A″/>  </data> </item> <item name=″102A″ template=″multiItem_Template″ area=”item”>  <data>   <multiChoice    correctAnswer=″B″    URI=″..\itembank/itembank.htm#102A″/>  </data> </item>

The XXL source above defines two items, “101A” and “102A”. Both items use the same template “multiItem_Template” and area “item”, both of which were defined in the previous example. Both items define a third level of data for the amalgamation. For example, the item named “101A” defines two previously undefined attributes: “correctAnswer” and “URI”. Item “101A” also overrides two previously defined attributes: maxResponses, minResponses and autoPrompt. (It should be noted that the data “maxResponses,” “minResponses,” and “autoprompt” are typically defined in the XXL language initializing a multi-choice item plugin 156 stored in data storage 906 under plugins branch 900. This XXL language is not shown.) The second item, “102A”, only defines the two previously undefined attributes. Item “102A” relies on amalgamation for the other attribute definitions, “maxResponses,” “minResponses, and “autoPrompt”.

FIG. 32 is a flow chart illustrating the overall process for amalgamation of visible plugins, denoted generally by reference numeral 1560. A first segment of the test specification and content, stored under plugins branch 900 is validated by the appropriate visible plugin 150, step 1561. A second segment of the test specification and content, stored under area storage 764 in templates branch 750, is then validated by the same visible plugin 150, step 1562. A third segment of the test specification and content, stored either under groups branch 850 (for display plugins 152 or helm plugins 156) or under items branch 650 (for item plugins 156), are validated by the same visible plugin 150, step 1563. The first segment, second segment, and third segment are then amalgamated, step 1564. The amalgamated segment is validated by the visible plugin 150 to determine whether the amalgamated segment forms a complete and valid set, step 1565. During delivery of the test, the first segment, second segment, and third segment are reamalgamated, step 1566, and the reamalgamated segment is delivered to the examinee, step 1567.

3) Amalgamation Process

FIG. 33 shows the flow chart for amalgamation process 400. There are three basic steps in amalgamation process 400. First, plugin 150 validates partial exam source in exam source files 130, step 1460. Secondly, plugin 150 validates the complete amalgamated test specification and content in exam resource file 130, step 1470. Finally, test driver 110 and plugin 150 deliver the complete amalgamated test specification and content, step 1480. Steps 1460 and 1470 generally occur during exam compilation and step 1480 generally occurs during delivery of the test to the examinee. Of course, other sequences and/or functionality may be used and/or substituted in accordance with the functionality described herein.

To support amalgamation, plugins 150 implement generally either IPersistResourceSet interface 192 b or IPersistResourceStore interface 192 c. POLESS performs the actual amalgamation on either a property set or a storage element in exam resource file 120. IPersistResourceStream 192 a cannot generally be amalgamated in one embodiment of the invention, although other amalgamation possibilities are possible.

FIG. 34 illustrates the process for exam source validation, step 1460, in greater detail, in accordance with one embodiment. Plugin 150 receives partial exam source from exam source files 140 through XXL compiler 140, step 1462. XXL compiler asks plugin 150 to validate the partial exam source using IPlugin 150::ValidateSource( ) call 1432 (FIG. 29). Plugin 150 determines whether or not the exam source is valid by comparing the exam source to the XXL schema, as previously described, step 1463. If the partial exam source is not valid, plugin 150 throws, for example, a structured COM error; step 1464, and the compilation is aborted.

Plugin 150 generally validates that what is present in the partial exam source is correctly formatted. Plugin 150 does not generally validate that all required source elements are present, only that what is present is legal. Plugin 150 also does not validate that attributes do not conflict. Conflict between elements cannot yet be determined since the amalgamated final view of plugin 150 data has not yet been established.

If the partial exam source is valid, XXL compiler creates the appropriate storage element via POLESS, step 1466. The storage element type is determined base on the IPersistResource interface 192 plugin 150 implements. If plugin 150 implements IPersistResourceSet interface 192 b, the data will persist to exam resource file 120 as a property set. If plugin 150 implements IPersistResourceStore interface 192 c, the data will persist to exam resource file 120 as a storage element. XXL compiler 140 then implements the IPersistResourceStore::Save( ) call or the IPersistResourceSet::Save( ) call, both calls being denoted by reference numeral 1434 in FIG. 29. Plugin 150 saves the compiled content and specification to exam resource file 120 through the POLESS object passed, step 1468.

FIG. 35 illustrates the process for complete amalgamated test specification and content validation, step 1470, in greater detail, in accordance with one embodiment. In step 1470, data stored in exam resource file 120 is amalgamated for validation. The purpose of this step is the validation of the amalgamated vector of storage elements to provide a complete specification and content for plugin 150. XXL compiler 140 calls for creation of an amalgamation storage vector, step 1472, using the calls cFileRoot::StorageAmalgamatedGet( ) or cFileRoot::PropertystorageAmalgamatedGet( ) (See cRoot class 400 in FIG. 10.) XXL compiler 140 then adds storage elements or property sets to the amalgamation storage vector, step 1474. These storage elements and sets were previously stored in exam resource file 120 by the plugin 150, step 1468 (FIG. 34).

XXL compiler 140 will amalgamate, for example, one to three storage elements or property sets depending on the type of plugin 150 at issue. As described above, for invisible plugins 150, XXL compiler 140 will amalgamate up to two storage elements or property sets. For visible plugins 150, XXL compiler 140 will amalgamate up to three storage elements or property sets. XXL compiler 140 uses the cStorageAmalgamated::StorageAdd( ) call to add a storage element to a storage amalgamation and the cPropertyStorageAmalgamated::PropertyStorageAdd( ) call to add an element to a property set amalgamation. (See cStorageAmalgamated class 404 and cPropertyStdrgeAmalgamated class 416 in FIG. 10.) The data contained in the storage elements or property sets is amalgamated according to the rule of amalgamation. The rule of amalgamation states that a later define element replaces an earlier defined element of the same name, as shown in the previous example of amalgamation for item plugin 156. Alternative amalgamation rules may optionally be used.

XXL compiler 140 determines whether or not the last storage element or property set has been added to the amalgamation storage vector, step 1475. If the amalgamation is complete, XXL compiler 140 passes the amalgamated POLESS object stored in the amalgamation storage vector to the IPersistResourceStore::ValidateResource( ) call or the IPersistResourceSet::ValidateResource( ) call, both calls being denoted by reference numeral 1438 in FIG. 29. XXL compiler 140 queries the amalgamation for IStorage interface 344 or IPropertyStorage interface 413. The appropriate interface is passed to plugin 150 in the validation call. Plugin 150 uses this virtual storage or property set to perform the validation on the amalgamated POLESS object.

Plugin 150 validates that the amalgamated POLESS object forms a complete and valid set, step 1478. Otherwise, plugin 150 throws an error, for example, a structured COM error, if the combination of content does not create a complete and valid set. Plugin 150 determines what is required for a complete and valid set. Referring to the previous example of item “101A”, the associated item plugin 156 requires “correctAnswer,” “autoPrompt,” and “URI” for completeness. Therefore, all of these attributes must be defined within the amalgamation storage vector to form a complete and valid set. The attributes need not exist at the same level in the exam source so long as they exist in the final amalgamation. “MaxResponses” and “minResponses” are not required for completeness. However, for a valid set, the value assigned to “maxResponses” must be greater than or equal to the value assigned to “minResponses”. The validity of these attributes can only be checked on the amalgamation since “maxResponses” and “minResponses” can be defined at different levels in the exam source.

FIG. 36 illustrates the process for delivery of amalgamated test specification and content for delivery, step 1480, in greater detail, in accordance with one embodiment. In step 1480, the exam resource data in exam resource file 120 is amalgamated for delivery. The purpose of this step is the delivery of the exam using the amalgamated plugin 150 specification and content. Test driver 110 calls for creation of an amalgamation storage vector, step 1482, using the calls cFileRoot::storageAmalgamatedGet( ) or cFileRoot::PropertystorageAmalgamatedGet( ) (See cRoot class 400 in FIG. 10..) Test driver 110 then adds storage elements or property sets to the amalgamation storage vector, step 1484.

Test driver 110 will amalgamate one to three storage elements or property sets depending on the type of plugin 150 at issue. As described above, for invisible plugins 150, XXL compiler 140 will amalgamate up to two storage elements or property sets. For visible plugins 150, test driver 110 will amalgamate up to three storage elements or property sets. Test driver 110 uses the cStorageAmalgamated::StorageAdd( ) call to add a storage element to a storage amalgamation and the cPropertyStorageAmalgamated::PropertyStorageAdd( ) call to add an element to a property set amalgamation. (See cStorageAmalgamated class 404 and cPropertyStorageAmalgamated 416 in FIG. 10.) The data contained in the storage elements or property sets is amalgamated according to the rule of amalgamation, as described previously.

Test driver 110 determines whether or not the last storage element or property set has been added to the amalgamation storage vector, step 1486. If the amalgamation is complete, test driver 110 passes the amalgamated POLESS object to the IPersistResourceStore::Load( ) call or the IPersistResourceSet::Load( ) call, step 1488 (see FIG. N). Plugin 150 can safely assume a full set of data in the amalgamated POLESS object because the amalgamated data was validated in step 1470 (FIG. 35). Test driver 110 queries the amalgamation for IStorage interface 344 or IPropertyStorage interface 413. The appropriate interface is passed to plugin 150 in the IPersistResourceStore::Load( ) call or the IPersistResourceSet::Load( ) call. Plugin 150 uses this virtual storage element or property set to enable delivery of the test, never realizing that the POLESS object is an amalgamation.

FIG. 37 illustrates three examples of amalgamation of property sets. Property set 1500 contains “prompt” information for an item plugin 156. In the level 1 specification, “prompt” is assigned the value “select best” in data storage 906 under plugins branch 900 in exam resource file 120. In the level 2 specification, template A and template B are defined, which use item plugin 156. Template A is used for item “101A” and template B is used for items “102A” and “103A”.

Property set 1502 contains “min” information for item plugin 156 regarding item “101A”. In the level 2 specification for item “101A”, “min” is assigned the value “1” in data storage 772 under templates branch 750 in exam resource file 120. Continuing with item “101A”, property set 1504 contains “correctAnswer” and “URI” information for item plugin 156 regarding item “101A”. In the level 3 specification for item “101A”, “correctAnswer” is assigned the value “A” and “URI” is assigned the value “items.htm#101A” in data storage 662 under items branch 650 in exam resource file 120.

Virtual property set 1506 represents the amalgamated property sets from levels 1, 2, and 3 for item “101A”. Virtual property set 1506 contains “min,” “prompt,” “correctAnswer,” and “URI” information for item plugin 156 regarding item “101A”. In the amalgamated POLESS object, “prompt” has the value “select best” from the level 1 specification, “min” has the value “1” from the level 2 specification, and “correctAnswer” has the value “A” and “URI” has the value “items.htm#101A” from the level 3 specification. Item plugin 156 for item “101A” never has a value assigned for the attribute “max”.

Property set 1508 contains “min,” “max,” and “prompt” information for item plugin 156 regarding items “102A” and “103A”. In the level 2 specification for items “102A” and “103A”, “min” is assigned the value “2,” “max” is assigned the value “2,” and “prompt” is assigned the value “pick 2” in data storage 772 under templates branch 750 in exam resource file 120. Continuing with item “102A”, property set 1510 contains “correctAnswer” and “URI” information for item plugin 156 regarding item “102A”. In the level 3 specification for item “102A”, “correctAnswer” is assigned the value “B” and “URI” is assigned the value “items.htm#102A” in data storage 662 under items branch 650 in exam resource file 120.

Virtual property set 1514 represents the amalgamated property sets from levels 1, 2, and 3 for item “102A”. Virtual property set 1514 contains “min,” “max,” “prompt,” “correctAnswer,” and “URI” information for item plugin 156 regarding item “102A”. In the amalgamated POLESS object, “min” has the value “2,” “max” has the value “2,” and “prompt” has the value “pick 2” from the level 2 specification. It should be noted that the final value for “prompt” was determined from the level 2 specification which overrides the initial value assigned to “prompt” in the level 1 specification, which was “select best”. “CorrectAnswer” has the value “B” and “URI” has the value “items.htm#102A” from the level 3 specification.

Property set 1512 contains “max,” “prompt,” “correctAnswer,” and “URI” information for item plugin 156 regarding item “103A”. In the level 3 specification, “max” is assigned the value “5,” “prompt” is assigned the value “select best,” “correctAnswer” is assigned the value “C,” and “URI” is assigned the value “items.htm#103A” in data storage 662 under items branch 650 in exam resource file 120.

Virtual property set 1516 represents the amalgamated property sets from levels 1, 2, and 3 for item “103A”. Virtual property set 1516 contains “min,” “max,” “prompt,” “correctAnswer,” and “URI” information for item plugin 156 regarding item “103A”. In the amalgamated POLESS object, “min” has the value “2” from the level 2 specification. “Max” has the value “5” from the level 3 specification. The value assigned to “max” in the level 3 specification overrides the value assigned to “max” in the level 2 specification, which was “2”. “Prompt” has the value “select best” from the level 3 specification. The value assigned to “prompt” in the level 2 specification overrides the value assigned to “prompt” in the level 1 specification, which was “select best”. However, the value assigned to “prompt” in the level 3 specification overrides the value assigned to “prompt” in the level 2 specification, which was “pick 2”, bringing the value for “prompt” back to the value originally assigned in level 1, “select best”. “CorrectAnswer” has the value “C” and “URI” has the value “items.htm#103A” from the level 3 specification.

The many features and advantages of the invention are apparent from the detailed specification, and thus, it is intended by the appended claims to cover all such features and advantages of the invention, which fall within the true spirit and scope of the invention. Further, since numerous modifications and variations will readily occur to those skilled in the art, it is not desired to limit the invention to the exact construction illustrated and described, and accordingly, all suitable modifications and equivalence may be resorted to, falling within the scope of the invention. 

1-101. (canceled)
 102. A computer-implemented test system comprising: a storage device comprising a first storage location and a second storage location, the first storage location storing a first segment of a test definition language and the second storage location storing a second segment of the test definition language, wherein the first segment and the second segment define computer based test data; a test packager, in operative data communication with the storage device that, during production of the at least one test, transmits the first segment and the second segment of the test definition language to a validation expansion module to validate formatting of the test definition language, amalgamates the first storage location and the second storage location and stores an amalgamated segment of the test definition language in a first virtual storage location, and transmits the amalgamated segment to the validation expansion module such that the validation expansion module is capable of determining whether the amalgamated segment forms a complete and valid set of the first segment and second segment of the test definition language; and a test driver, in operative data communication with the storage device, comprising an executable code that controls functionality that enables the test driver to manage and deliver the at least one test to an examinee.
 103. The system of claim 102, wherein the amalgamation of the test definition language includes storing the data in an object-linking and embedding (OLE) structured storage format. 